Personal video recording with further compression of recorded shows

ABSTRACT

Automated personal video recording on a personal video recorder, including recording shows, each show having an original compression level; further compressing a recorded show to a new compression level, the new compression level being higher than the recorded show&#39;s original compression level, thereby making available free space; and recording at least part of a new show in free space made available by further compressing the recorded show. Embodiments include recording a show having a compression level and increasing the show&#39;s compression level while recording.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is related to the following co-pending U.S.Patent Applications, filed on the same day as the present application,having the same inventors and assignee, and which are herebyincorporated by reference:

-   -   1. Patent application Ser. No. 10/180,143, titled “Personal        Video Recording With Storage Space Loans”    -   2. Patent application Ser. No. 10/180,362, titled “Personal        Video Recording with Recovery of Displayed Storage Space”    -   3. Patent application Ser. No. 10/180,145, titled “Personal        Video Recording with Pools and Groups”    -   4. Patent application Ser. No. 10/180,164, titled “Personal        Video Recording With Storage Space Requirement Checking”    -   5. Patent application Ser. No. 10/180,591, titled “Personal        Video Recording With Apportioned Loans of Storage Space”

BACKGROUND OF THE INVENTION

1. Field of the Invention

The field of the invention is data processing, or, more specifically,methods, systems, and products for automated personal video recording.

2. Description of Related Art

In the current art of the personal video recorder (“PVR”), the storagespace available upon which to record television shows or other videocontent (“shows”) is a limited resource. PVRs are relatively expensiveand therefore are typically shared by more than one user. The Tivo™system is an example of such a PVR, and today the Tivo™ system ismarketed by the number of hours of video content it can record,typically 20, 30, or 50 hours. In a setting with more than one user, therecording time available on typical PVRs is not configured or controlledby user allocation, which causes problems. One user may use adisproportional share of the storage space available for recording videocontent, leaving little or none for other users of the recorder. Itwould be advantageous if there were ways to configure or control storagespace to facilitate use by multiple users, allowing for multiple usersto share the storage resources collision-free, with little risk oferasing or overwriting someone else's recorded shows.

In addition, it is useful to note that estimates of storage spacerequired for recording a particular show are made in dependence upon anestimated compression level. It would be advantageous, therefore, tohave means and methods of administering the risk that an estimate ofcompression level and therefore an estimate of storage space requirementwill be too small. Moreover, although such provisions are substantiallylacking in the prior art, it would be advantageous also to providevarious ways for users to aggregate their abilities to lend, borrow, andrecord shows. In addition, although such provisions are substantiallylacking in the prior art, it would be advantageous also to providevarious ways for users to lend storage space to other users and togroups of users. It would also be useful, particularly when free spacefor lending is scarce, for users to be able to recover used space sothat it could be used in recording additional shows.

SUMMARY OF THE INVENTION

PVRs according to exemplary embodiments of the invention typicallyimplement methods for automated personal video recording on a multi-userpersonal video recorder, including recording shows. The recorded showseach show has an original compression level. Some embodiments includecompressing a recorded show to a new compression level, the newcompression level being higher than the recorded show's originalcompression level, thereby making available additional free space foruse in recording. Such embodiments include recording at least part of anew show in free space made available by further compressing therecorded show.

In exemplary embodiments, a new show's storage space requirement exceedsan amount of free space available for recording the new show by adeficit amount. Such embodiments include borrowing a loan amount, theloan amount being less than the deficit amount. Such embodimentstypically include selecting the recorded show. In such embodiments,selecting the recorded show typically includes selecting a show havingan original compression level lower than a highest supported compressionlevel in a PVR.

In exemplary embodiments, the recorded show typically includes anoriginal video file and further compressing the recorded show includescalling software routines in an API for a codec. In such embodiments,the recorded show typically includes an original video file havingoriginal encoding parameters including an original encoding type, andfurther compressing the recorded show includes converting the originalvideo file into a new video file having new encoding parametersoptionally including a new encoding type, and deleting the originalvideo file.

Exemplary embodiments of the invention include recording a show having acompression level, and increasing the show's compression level whilerecording. In such embodiments, the show comprises a duration andincreasing the show's compression level typically includes tracking arecording period for the show and tracking actual storage space usedduring the recording period. PVRs according to such embodiments includecomparing the storage space used with an amount of storage spaceprojected to be used during the tracked recording period. Such PVRs,when the tracked recording period is at least equal to a space checkthreshold multiplied by the duration, increase the show's compressionlevel if the storage space used is greater than the storage spaceprojected to be used.

In exemplary embodiments of the invention, recording a show includesencoding a video stream to a first video file. In such embodiments, theencoding is carried out in dependence upon the values of factorsaffecting compression level. In such embodiments, increasing the show'scompression level typically includes changing the values of the factorsaffecting compression level, changing the compression level of thesecond video file, and redirecting the video stream to a second videofile. Such embodiments often include further compressing the first videofile to the compression level of the second video file and concatenatingthe second video file to the first video file.

The foregoing and other objects, features and advantages of theinvention will be apparent from the following more particulardescriptions of exemplary embodiments of the invention as illustrated inthe accompanying drawings wherein like reference numbers generallyrepresent like parts of exemplary embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1 a and 1 b are pictorial representations of aspects ofinformation handling systems in which exemplary embodiments of thepresent invention may be implemented.

FIG. 2 a is a block diagram of an example embodiment of a PVR accordingto the present invention.

FIG. 2 b is a pie chart illustrating an example of storage spaceallocation.

FIG. 3 depicts data structures as related records useful in exemplaryembodiments of the present invention.

FIG. 4 is a flow chart depicting a method of personal video recording.

FIG. 5 is a flow chart depicting an example method of selecting lenders.

FIG. 6 is a flow chart depicting an example method of selecting multiplelenders from whom to borrow loan amounts totally at least a deficitamount.

FIG. 7 is a flow chart depicting an example method of selecting a lenderaccording to a lending priority.

FIG. 8 is a flow chart depicting an example method of selecting a lenderaccording to the ratio of free space to a deficit amount.

FIG. 9 is a flow chart depicting an example method of returning borrowedstorage space from a borrower to a lender.

FIG. 10 a depicts data structures in records representing examples ofapproximate compression levels, organized with reference to an HDTVsource.

FIG. 10 b depicts data structures in records representing examples ofapproximate compression levels, organized with reference to an NTSCsource.

FIG. 11 is a flow chart depicting a method of personal video recordingincluding recalculating a storage space requirement.

FIG. 12 is a flow chart depicting an alternative method of personalvideo recording including recalculating a storage space requirement.

FIG. 13 depicts data structures for a PVR system-level profile and forgenre-keyed space checking records related one-to-many to the PVRprofile, data structures useful in various exemplary embodiments of thepresent invention.

FIG. 14 is a flow chart depicting an exemplary method of incrementingstorage space requirements in dependence upon genre.

FIG. 15 is a flow chart depicting a further exemplary method ofincrementing storage space requirements in dependence on genre.

FIG. 16 is a pie chart depicting an example of unallocated storage spaceand storage space allocations among user's, a pool, and a group.

FIG. 17 is a flow chart depicting an exemplary method of personal videorecording including borrowing storage space wherein at least one lenderis a pool.

FIG. 18 is a flow chart depicting an exemplary method of assigningstorage space to a pool.

FIG. 19 is a flow chart depicting an additional exemplary method ofassigning storage space to a pool.

FIG. 20 depicts exemplary data structures useful in various embodimentsutilizing pools.

FIG. 21 a depicts exemplary data structures useful in variousembodiments utilizing groups.

FIG. 21 b depicts alternative exemplary data structures useful invarious embodiments utilizing groups.

FIG. 22 is a flow chart depicting an exemplary method of creating agroup, including the alternatives of allocating group storage space fromusers' space and assigning group storage space from unallocated space.

FIG. 23 is a flow chart depicting alternative exemplary methods ofallocating a show's storage space requirements among group members.

FIG. 24 is a flow chart depicting exemplary methods of reallocating ashow's storage space requirements among group members in the event thatone or more members opt out of a storage space allocation.

FIG. 25 is a flow chart depicting alternative exemplary methods ofallocating a loan among group members.

FIG. 26 is a flow chart depicting exemplary methods of reallocating ashow's group loan among group members in the event that one or moremembers opt out of responsibility for group storage.

FIG. 27 sets forth example data structures useful in various embodimentsof the present invention.

FIG. 28 is a flow chart depicting an exemplary method of freeingdisplayed storage space for use in recording shows.

FIG. 29 is a flow chart depicting an exemplary alternative method ofborrowing a loan amount of storage space, less than a deficit amount,and freeing displayed space.

FIG. 30 is a flow chart and schematic diagram of storage spacerequirements depicting an alternative method of freeing displayed spaceof a show while recording and viewing a show.

FIG. 31 is a flow chart depicting an exemplary method of identifyingdisplayed space.

FIG. 32 is a flow chart depicting an alternative exemplary method ofdiscarding displayed frames.

FIG. 33 is a flow chart depicting a further alternative exemplary methodof discarding displayed frames.

FIG. 34 is a diagram of a prior art structure of MPEG video.

FIG. 35 is a flow chart depicting an exemplary method of furthercompressing a show.

FIG. 36 is a flow chart depicting an exemplary alternative method ofborrowing a loan amount of storage space, less than a deficit amount,and further compressing a recorded show.

FIG. 37 is a flow chart depicting a further alternative exemplary methodof further compressing a show.

FIG. 38 is a flow chart depicting an exemplary method of increasingcompression level while recording a show.

FIG. 39 is a flow chart depicting an exemplary method of increasingcompression level while recording a show.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS Introduction

The present invention is described to a large extent in thisspecification in terms of methods for automated personal videorecording. Persons skilled in the art, however, will recognize that anycomputer system that includes suitable programming means for operatingin accordance with the disclosed methods also falls well within thescope of the present invention.

Suitable programming means include any means for directing a computersystem to execute the steps of the method of the invention, includingfor example, systems comprised of processing units and arithmetic-logiccircuits coupled to computer memory, which systems have the capabilityof storing in computer memory, which computer memory includes electroniccircuits configured to store data and program instructions, programmedsteps of the method of the invention for execution by a processing unit.The invention also may be embodied in a computer program product, suchas a diskette or other recording medium, for use with any suitable dataprocessing system.

Embodiments of a computer program product may be implemented by use ofany recording medium for machine-readable information, includingmagnetic media, optical media, or other suitable media. Persons skilledin the art will immediately recognize that any computer system havingsuitable programming means will be capable of executing the steps of themethod of the invention as embodied in a program product. Personsskilled in the art will recognize immediately that, although most of theexemplary embodiments described in this specification are oriented tosoftware installed and executing on computer hardware, nevertheless,alternative embodiments implemented as firmware or as hardware are wellwithin the scope of the present invention.

Definitions

In this specification, the terms “field” and “data element,” unless thecontext indicates otherwise, generally are used as synonyms, referringto individual elements of digital data. Aggregates of data elements arereferred to as “records” or “data structures.” Aggregates of records arereferred to as “tables” or “files.” Aggregates of files or tables arereferred to as “databases.”

The terms “borrow,” “lend,” and “loan,” subject to context, generallyimply a relatively shorter term rearrangement of storage space effectedunder automated control of a PVR. The term “allocate,” subject tocontext, generally implies a relatively longer term rearrangement ofstorage space effected by users' manual inputs through user interfaces.An example of borrowing is a PVR's determination at record time that adeficit of storage space exists that needs to be cured before recordingproceeds. If the cure is a rearrangement of storage space to be reversedafter users view a show, then the cure is said to be a ‘borrowing’ or a‘loan.’ An example of an allocation is a user's manual instructionthrough a keyboard or a remote control device, in response to promptscreens, and by use of data input screens on a display device, to assigna portion of unallocated storage space to a user or to a pool.

“Cinepak” is a popular codec originally developed by SuperMac, Inc.

“Codec” is an industry-standard term referring to “encoder/decoder,” orperhaps more legibly, “coder/decoder”. Codecs are means and methods forencoding and decoding video with audio. Codecs are implemented inhardware or in software. The codec illustrated at reference 176 in FIG.2 a, shown in a system or apparatus diagram, is implicitly a hardwarecodec. Hardware codecs, like other co-processors, tend to offload CPUburden and render overall PVR operation more efficient. Software-onlycodecs are freely available for downloading from various sources on theInternet. It is probably an accurate general description that softwarecodecs tend to be less expensive than hardware codecs, while hardwarecodecs tend to be more efficient. There are many codecs, including, forexample, Cinepak, Motion JPEG, and, of course, MPEG. PVR operations arevideo-intensive, so that hardware codecs will be common in PVRsaccording to embodiments of the present invention, although the use ofsoftware codecs is also well within the scope of the present inventionsand actually quite likely in a variety of cost-conscious embodiments.

Codec functions include compression and decompression. When show isencoded, it is converted to a compressed format suitable for storage ortransmission; when it is decoded it is converted to a non-compressed(raw) format suitable for presentation. Each codec has certain inputformats that it can handle and certain output formats that it cangenerate. In some situations, a series of codecs are used to convertfrom one format or compression level to another.

“DVD” stands for ‘Digital Versatile Disc’ or ‘Digital Video Disc,’ animproved storage standard that holds at least of 4.7 gigabytes, enoughfor a full-length movie. DVD storage, like CD-ROM storage, is typicallyeventually optical, although the format does not strictly requiredoptical storage and is often implemented in other kinds of storage,magnetic or electronic, at least as interim measures. The DVDspecification supports disks with capacities of from 4.7 gigabytes to 17gigabytes and access rates of 600 KBps to 1.3 MBps. DVD drives arebackward-compatible with CD-ROMs. That is, DVD players can play oldCD-ROMs, CD-I disks, and video CDs, as well as DVD-ROMs. DVD players canalso read CD-R disks. DVD may be pertinent to PVRs according toembodiments of the present invention because DVD, like HDTC, uses MPEG-2to compress video data.

“Compression” as the term is used in this disclosure refers to theoverall effect of all applicable techniques for video file sizereduction, including, for example, reduction of color space, reductionof frame rate, reduction of resolution, reduction of audio quality, andchanges in compression algorithms or compression algorithm parameters assuch. There are many ways, as will occur to those of skill in the art,to reduce file size by manipulation of compression algorithms and theparameters of compression algorithms. The use of the term “compression”in this disclosure, however, subject to context, of course, is generallybroader than mere manipulation of compression algorithms.

“Compression level” refers to an estimated compression level calculatedon the basis of a show's duration and an estimated compression level forthe recorded content of the show. Unless the context requires otherwise,the term “compression level” means “estimated compression level.”

“Compression algorithm” refers to a particular type of compressiontechnique, including lossy as well as lossless compression, includingfor example, Lempel-Zif-Welch compression, which is the compressiontechnique used in the popular graphics file format known as “GIF”;various flavors of Lempe-Zif compression such as LS-77 and LZ-78, LZ-78being a ‘dictionary’ compression technique used in many popularapplications such as the well-known ‘zip’ utilities; run-lengthencoding; and Huffinan encoding.

“ID” abbreviates “identification,” meaning ‘identification code’ oridentification field. It is a style of reference in this disclosure torefer to user identification codes as “user IDs.” By convention in thisdisclosure, the field name “UserID” is used to store a user ID. That is,for example, the UserID field 190 in the example user profile 202 inFIG. 3 contains a user ID of a registered user on a PVR. When a user IDfor a borrower is stored in a data element in computer memory, it is aconvention in this disclosure to refer to that user ID, a borrower'sidentification, that is, as a “borrower ID.” Similarly, lendersidentifications are often termed “lender IDs.” “Borrower IDs” and“lender IDs” are user IDs for roles of users as lenders, borrowers,owners, viewers, and so on. That is, for example, borrowers and lendersare users having user IDs. When a user acts as a borrower, depending onthe context, the user is generally said then to have a borrower ID. Whenwe name a field to store a borrower ID, we adopt the convention ofnaming the field “BorrowerID.” The lending authorization records atreference 220 in FIG. 3, for example, include a LenderID field 222 whichcontains a user ID of a user authorizing lending.

“JPEG” stands for Joint Photographic Experts Group, the original name ofthe committee that developed the standard. JPEG is a data compressionstandard for graphic images. JPEG can reduce files sizes to about 5% oftheir uncompressed size, although some detail is lost in thecompression.

“Motion JPEG” or “MJPEG” extends the JPEG standard by supporting video.In Motion JPEG, each video frame is stored using the JPEG format. Inthis regard, note that the 5% compression estimate for JPEG is theeffect of the compression algorithm alone, without regard to frame rate,resolution, and so on.

“MPEG” stands for ‘Moving Picture Expert Group,’ a working group under“ISO,” the International Organization for Standardization and “IEC,” theInternational Electrotechnical Commission. What is commonly referred toas “MPEG video” actually includes three standards, MPEG-1, MPEG-2, andMPEG-4. MPEG-1 and MPEG-2 are similar. They both work on motioncompensated block-based transform coding techniques. MPEG-4 differs inits use of software image construct descriptors for target bit-rates inthe very low range, less than 64 Kb/sec.

“MPEG-1” was originally optimized to work at video resolutions of352×240 pixels at 30 frames/sec (NTSC based) or 352×288 pixels at 25frames/sec (PAL based), commonly referred to as Source Input Format(SIF) video. The MPEG-1 resolution is not limited to the above sizes andin fact may go as high as 4095×4095 at 60 frames per second. MPEG-1'sbit-rate is optimized for applications of around 1.5 megabits persecond, although MPEG-1 can be used at higher rates if required. MPEG-1is defined for progressive frames only, and has no direct provision forinterlaced video applications, such as are used in broadcast televisionapplications.

“MPEG-2” addresses issues directly related to digital televisionbroadcasting, such as the efficient coding of field-interlaced video andscalability. MPEG-2's target bit-rate is higher than MPEG-1's, between 4and 9 Mb/sec, resulting in potentially very high video quality. MPEG-2is based upon ‘profiles’ and ‘levels.’ The profile defines bitstreamscalability and colorspace resolution, while the level defines imageresolution and maximum bit-rate per profile. Probably the most commondescriptor in use currently is ‘Main Profile, Main Level’ (MP@ML), whichrefers to 720×480 resolution video at 30 frames/sec, at bit-rates up to15 Mb/sec for NTSC video. Another example of an MPEG-2 descriptor incommon use is the HDTV resolution of 1920×1080 pixels at 30 frame persecond, at bit-rates up to 80 megabits per second. This HDTV example isa ‘Main Profile, High Level’ (MP@HL) descriptor. A complete table of thevarious legal combinations can be found in reference².

“NTSC” stands for a video standard promulgated by the NationalTelevision Standards Committee. The Committee is responsible for settingtelevision and video standards in the United States. In Europe and therest of the world, the dominant television standards are PAL and SECAM.The NTSC video standard defines a composite video signal with a framerate of 30 frames/second implemented as 60 interlaced half-frames persecond. Each frame contains 525 lines and can contain 16 milliondifferent colors. A newer digital television standard is called “HDTV”for High Definition Television, supporting higher resolutions than NTSC.

“Show” means any recordable or distributable electronic or digitalcontent including television broadcasts, movies, CD contents, DVDrecordings, cable transmission, satellite transmissions, commercialvideo clips, audio, multi-media programming, and the like. Shows includeany image or series of images delivered to users through any mechanismor means, including associated audio or other multi-media content.

Unless the context requires otherwise, “user” means ‘registered user,’that is, a user having within a PVR a representative user profile suchas those illustrated by the record structure at reference 202 on FIG. 3.Readers will notice that there are no logons required within the scopeof the present invention, although logons are permitted. Unregisteredusers therefore are permitted in many embodiments to view shows recordedby other users. The benefit of allowing viewing by unregistered viewersis that visiting relatives do not need to have user profiles installedfor them. The can just sit down and watch TV. In many embodiments,however, access controls are installed that do as a practical matterrequire logons, despite the fact that logons are optional within theinvention itself. Examples of configurations of PVRs, according toembodiments of the present invention, that require logons for accesscontrol are PVRs that control children's viewing hours and PVRs thatcontrol access to mature content by younger viewers.

“Video” as the term is used in this disclosure, and according tocontext, generally includes audio.

Borrowing Storage Space

With reference now to the figures, and in particular with reference toFIGS. 1 a and 1 b, pictorial representations of an information handlingsystem in which an exemplary embodiment of the present invention may beimplemented are depicted. Embodiments of the present invention generallyare implemented as information handling systems that include automatedcomputing machinery. For simplicity, however, and because suchinformation handling systems with automated computing machinery willoften in fact comprise personal video recorders of one form or another,this disclosure refers generally to implementations of embodiments ofthe present invention as personal video recorders or “PVRs.”

FIG. 1A is a pictorial representation of a typical context ofinstallation of one kind of PVR according to the present invention. ThePVR 106 of FIG. 1 a is a set top box, similar in size and shape to acable television box or a video cassette recorder (“VCR”). PVR 106 isconnected to a television 102 for display on display screen 101 oftelevision shows, movies, or other content, as well as display ofoperational information regarding the PVR itself and its stored orrecorded content. By “stored content” or “recorded content” is meant anyinformation or entertainment content capable of being recorded in anenvironment comprising automated computing machinery, including, forexample, broadcast television shows, cable television shows, motionpictures, personal video clips from video recorders, audio and musicpieces, video/audio downloaded from Internet locations, and materialsourced from optical storage such as compact discs. In fact, the examplePVR 106 shown in FIG. 1 a includes a read/write compact disc drivesupporting removable media. Again for simplicity of reference, “storedcontent” is often referred to in this disclosure as “shows.”

The PVR 106 is connected to the television 102 by cable 104. The cableconnection 104 can be for video and audio through a standard videocable, or for television broadcast frequencies through a standardcoaxial cable. A remote control unit 110 allows users to interact withand control the PVR 106. Remote control unit 110 emits infrared (“IR”)signals, although other kinds of remote control emissions are within thescope of the invention, including for example radio control. The examplePVR 106 includes an IR window 109 for receipt of information andinstructions from remote control unit 110. Functions provided by use ofthe remote control unit 110 include the ability to move a cursor on adisplay and select items shown on a display.

FIG. 1 b is a more detailed depiction of a remote control unit 110useful with various embodiments of the present invention. Similar to astandard remote control for a television set or a VCR, remote controlunit 110 includes a “Menu” button for access to a central set of menusand data entry screens for configuring the PVR, configuring userprofiles on the PVR, and scheduling shows. The “Up” and “Down” buttons113 and 115 allow users to change displays page-by-page rather than byscrolling line-by-line or item-by-item. Navigation buttons 114 supportscrolling. The “Select” button 116 is used to select a display itemafter paging and scrolling have located the item.

The remote control unit includes conventional numeric keys 131 as wellas buttons associated with television and recorded playback controlincluding a “Volume” control 132, a “Channel” selector 120, a “Mute”button 118, and buttons for “Play” 124, a rewind button called “Back”134, a fast forward button labeled “Fwd” 130, and a pause button 126.The “Record” button 122 is used to instruct the PVR to record a showtypically when the show has been selected, for example, throughnavigation through a series of display screens depicting televisionbroadcast schedules for televisions shows.

In the previous few paragraphs, we described an embodiment of thepresent invention as an information handling system with automatedcomputing machinery configured as a PVR, a set top box coupled to atelevision for display and user interaction and controlled by a remotecontrol unit. It is useful to understand that the set top boxconfiguration is not at all the only configuration of a PVR within thescope of the present invention, and to clarify this point, we ask thereader to consider PVRs implemented as software installed upon generalpurpose computers. In the case of a PVR embodied upon a general purposecomputer, the PVR is implemented as software installed in computermemory in a conventional fashion to embody the inventive steps of thepresent invention.

Although a PVR implemented as a set top box will include by specialdesign within the set top box all the hardware resources needed toimplement the steps of the invention and store content in accordancewith the invention, not all computers will possess such hardware. To theextent that any general purpose computer, however, and today many ofthem do, possesses sufficient resources to download, read from a compactdisc, receive cable television, or otherwise access recordable content,and sufficient resources to store such recordable content on hard disk,writable optical drives, or other storage media, then any generalpurpose computer can be configured as a PVR according to an embodimentof the present invention.

For PVRs embodied in general purpose computers according to the presentinvention, PVR controls are implemented through the usual user interfaceas provided in connection with any particular computer terminal,computer screen, computer keyboard, computer mouse, and so on. In thissense, general purpose computers include personal computers, portablecomputers, minicomputers, mainframes, laptop computers, handheldcomputers, personal digital assistants, wireless Internet-enabled cellphones, and so on.

FIG. 2 a sets forth a block diagram of automated computing machinerycomprising a PVR 106 according to an exemplary embodiment of the presentinvention. The PVR 106 of FIG. 2 a includes at least one computerprocessor 156 as well as random access memory 152 (“RAM”). Stored in RAM168 is a PVR application program 152 implementing inventive steps of thepresent invention.

Also stored in RAM 168 is an operating system 154. Embodiments of thepresent invention are directed towards personal video recording formultiple users. It will occur to readers skilled in the art that much ofthe work of administering user accounts for many users may bedownshifted to a multi-user operating system such as Unix, Linux, orMicrosoft NT™. The multi-user features of typical embodiments of thepresent invention, however, tend to be features of application software.PVRs according to embodiments of the present invention, therefore, mayuse single-user operating systems, such as Microsoft's Disk OperatingSystem or “DOS,” as well as multi-user operating systems, or evenoperating systems developed as special purpose systems just for use inPVR according to this invention. In this disclosure, we speak ofadministration of multiple users in terms of “user profiles,” todistinguish our application-level user administration from any operatingsystem's administration of ‘user accounts.’

The PVR 106 of FIG. 2 a includes storage space 166 for shows. Storagespace 166 can be implemented as hard disk space 170, optical drive space172, electrically erasable programmable read-only memory space(so-called ‘EEPROM’ or ‘Flash’ memory) 174, RAM drives (not shown), oras any other kind of computer memory capable of receiving and storingrecorded content as will occur to those of skill in the art.

The example PVR 106 of FIG. 2 a includes a subsystem for content capture167. This subsystem for content capture 167 is implemented in typicalembodiments according to content sources 182 and can include in variousembodiments a broadcast television tuner for receipt of broadcasttelevision 158, a cable box for receipt of cable television 160, asatellite receiver for receipt of satellite television 162, and anInternet connection for downloading recordable content from the Internet164.

The example PVR of FIG. 2 a includes a codec 176, which can take theform of a video card plugged into the system bus of a personal computer,or other forms as will occur to those of skill in the art. The codec 176provides video and audio output from recorded shows in storage space 166to an input/output interface 178. The codec 176 can also provide changesin video compression or video quality as needed in particular instances.The input/output interface provides video and audio output to a displaydevice 180. In the case of PVRs implemented with connection totelevisions, the display device 180 is a television. In the case of PVRsimplemented as general purpose computers, the display device is oftenimplemented as a computer screen. The display device 180 is any device,as will occur to those of skill in the art, capable of displaying videoand audio content.

The example PVR of FIG. 2 a includes an input/output interface 178. Theinput/output interface 178 in PVRs implemented as general purposecomputers is a computer interface including, for example, conventionalsoftware drivers and computer hardware for controlling output to displaydevices 180 such as computer screens, as well as user input from userinput devices 181 such as computer keyboards and computer mice. In thecase of PVRs as set top boxes, an input/output interface 178 comprises,for example, software drivers and computer hardware for controllingdisplays on display devices 180 such as television screens and userinput from user input devices 181 such as remote control devices (likethe one illustrated at reference 110 in FIG. 1 a and 1 b).

FIG. 3 illustrates several example data structures useful in variousembodiments of the present invention. Such data structures are part ofthe PVR application software in typical embodiments (reference 152 onFIG. 2 a) and are usually stored in RAM (168 on FIG. 2 a) or, forlonger-term or non-volatile storage, on a hard disk (170 on FIG. 2 a) orother non-volatile storage as will occur to those of skill in the art.The example data structures of FIG. 3, for clarity of explanation, areshown related as records in a database, although other data storagearrangements as will occur to those of skill in the art are possible,all such arrangements being well within the scope of the presentinvention.

FIG. 3 depicts an example user profile 202, useful for registeringmultiple users on PVRs. The user profile 202 represents a userregistered on the PVR in which the profile is installed and sets forthcharacteristics and limitations regarding the user and the user'sprivileges to operate the PVR. More specifically, the user profile 202includes data elements for storing a user identification or “UserID”190, a password or personal identification number called a “PIN” 192, auser privilege level 194, and content restrictions 196 on recordablecontent allowed for the user.

The PIN 192 is assigned to the user at registration time and is uniqueto the user. In PVRs implemented as set top boxes, it is common toutilize numeric PINs because they are easily entered through numerickeys on remote control units (reference 131 on FIG. 1 b). Numeric PINs,of course, are not a requirement of the invention. Clearly PVRsimplemented upon general purpose computers or any device having akeyboard, for example, would experience no particular benefit fromnumeric-only PINs or passwords.

The user privilege level 194 provides the capability of distinguishingprivileges according to class of user. That is, the user privilege level194 supports the establishment of classes of users having various levelsof privilege. A common example is a class of administrative users or‘super users’ who are privileged to edit the profiles of other users. Ina home setting, therefore, parents would often be super users privilegedto set content restrictions on children's profiles. In a businesssetting, system administrators in the Information Technology Servicesorganization would often be privileged to create and administer profilesfor users with normal usage privileges.

The example user profile 202 of FIG. 3 also provides several exampledata elements for recording characteristics of storage space availablefor recording shows on behalf of the user represented by the profile.The user profile 202 provides data elements for allocated space 198,used space 204, free space 206, borrowed space 208, loaned space 210, aBoolean indication whether the user authorizes lending to other usersstorage space allocated to the user 212, and a lending priority rating214.

The allocated space field 198 records the amount of storage spacepresently allocated to the user. It is usual, although not a requirementof the invention, that the allocated space is altered only by superusers, so that normal users avoid conflict risked by normal userschanging their own storage space allocations. An initial quantity ofallocated space is assigned to each user at registration time, when theuser's user profile is created. FIG. 2 b sets forth a pie chart 175showing an example of allocation of storage space in a residentialsetting. In the example allocation of FIG. 2 b, allocation of 100% ofthe storage space of a PVR within a family includes allocation of 80% ofthe storage space for parents (40% for father and 40% for mother) andallocation of 20% of the storage space for children (10% for a son and10% for a daughter).

As the user records shows in the user's allocated space, when a show isrecorded in a user's allocated storage space, some of the storage space,the space upon which the show is recorded, is said to be ‘used.’ Eachshow has a storage space requirement that uses some of a user'sallocated storage. The current total of the used space of all the showsrecorded for a user can be stored in the UsedSpace field 204. The freespace field 206 is provided for storing the difference between allocatedspace 198 and used space 204. When a PVR records a show for a user, thePVR increments UsedSpace 204 by the amount of the show's storagerequirement and decrements FreeSpace 206 by the same amount.

When the PVR records a show for a user whose FreeSpace is less than theshow's storage space requirement, it is an aspect of PVRs according toembodiments of the present invention that the user, acting as aborrower, can borrow space from another user, a lender. The amount ofstorage space that the user represented by the user profile 202 hasborrowed can be recorded in the BorrowedSpace field 208. Similarly, theamount of storage space that the user has loaned to other users can berecorded in LoanedSpace 210. Just as the PVR decrements FreeSpace 206when the PVR records a show for the user, the PVR also can decrementFreeSpace 206 when the PVR loans a portion of the user's allocated space198. In this example, therefore, the FreeSpace amount 206, that is, theamount of storage space available to a user for recording shows would bethe user's allocated space 198 minus the user's used space 204 minus theuser's loaned space 210. It will be discussed in more detail below, butit should be clear that when a user's free space is less than thestorage space requirement for a show to be recorded for the user, analternative process available to a PVR, in addition to borrowing spacefrom a lender, is to repossess space that the user previously loaned toborrowers. In the present example, such repossession would reduceLoanedSpace 210 and increment FreeSpace 206 by the amount of spacerepossessed.

The example user profile 202 of FIG. 3 also provides a Boolean dataelement LendingAuthorized 212 for indicating whether the userrepresented by the profile authorizes borrowings from the user'sallocated storage. A lending control such as the LendingAuthorizationfield 212 can be provided at the user level for users who may wish to,for example, simply exclude all lending from their allocated storage.Establishing a blanket lending authorization at the user level is afairly coarse quality of control, and it is possible within the scope ofthe present invention to establish more fine-grained controls overlending authorization.

An example of a more finely-grained lending authorization is depicted inthe lending authorization records 220 in FIG. 3. The example lendingauthorization records 220 are more finely-grained in that they representauthorizations to lend a specific maximum amount, identified in theMaximumLoan field 226, from a specific lender, identified by thelender's user ID in the LenderID field 222, to a specific borrower,identified by the borrower's user ID in the BorrowerID field 224. Anexample of a less finely-grained lending authorization is one in which aPVR is programmed to permit lending to any registered user. In terms ofthe example data structures of FIG. 3, lending to any user can beimplemented by permitting a ‘wild card’ entry in the BorrowerID field224 in the lending authorization records 220, such as, for example, anasterisk, ‘*,’ which is treated by the PVR as an indication that thelender 222 identified in the lending authorization record 220 authorizesloans to any user.

Of course other granularities are possible within the scope of thepresent invention, including, for example, lending authorizations havingvalidity periods with beginning dates and ending dates, or lendingauthorization for identified user groups or for users having certainlending priority levels. The possible settings are many, and any datastructure, encoding method, or granularity of lending authorization aswill occur to those of skill in the art is well within the scope of thepresent invention.

The example user profile 202 of FIG. 3 also provides a data elementcalled LendingPriority 214 for establishing lending priority ratings forusers. This data element can be used in algorithms to establish thesequence in which space otherwise authorized for lending will beborrowed or to exclude some loans on the basis of comparisons ofpriorities among users. By establishing two simple lending priorities,for example, lending priority rating ‘1’ and lending priority rating‘2,’ in a home setting, super users (parents, for example) can assignthemselves a higher lending priority rating than child users and eitherexclude all lending from parents to children or exclude lending tochildren as long as space is available for lending from children tochildren, so that children could only borrow from parents after usingall space allocated to children. A further example data structure, asystem-level profile, in this example called ‘PVR Profile’ 300, can beestablished to record PVR-level parameters. In this example, the PVRprofile includes a Boolean indication, LendingPriorityExcludes 302,whether user's lending priority ratings are to be used by the PVR toexclude all lending to users having lower priority ratings or justsequence the lending by requiring loans first from users with lowerpriority ratings.

The example data structures of FIG. 3 include show records 240. A showrecord 240 is a data structure representing a segment or clip ofrecorded content, such as video and audio, for example, a televisionshow or a motion picture. There are generally two sources of showrecords 240, user scheduling and preference recording. “User scheduling”is a user's entering through a user interface a title and recordingschedule for the show. The user interface will vary from PVR to PVR. Theuser interface, in PVRs implemented as set top boxes, is typically aremote control unit maneuvering a pointer over a scrolling list oftelevision shows on a television screen. The user interface, in PVRsimplemented as personal computers, is typically a keyboard, a mouse, anda computer screen upon which is displayed a mouse pointer used tohighlight and select from scrolling lists of television programs or websites hosting video clips of interest.

“Preference recording” is a PVR's being programmed to select and recordshows based upon previous indications of user preference. Previousindications of user preference are implemented, for example, as a genrepreference 260 in a user profile 202, causing a PVR so programmed, whena user has sufficient free space to support such recording, reading theuser's previously indicated preference for Comedy, Drama, ScienceFiction, or Sports, for example, scanning presently available sources,selecting the first show that matches the user's genre preference forwhich the user has sufficient free space, and recording that show. Inaccordance with the present invention, the PVR can be programmed toborrow space from another user if the user has insufficient free spaceto store the show.

Alternatively, to achieve even greater power to express particularpreferences, PVRs can support separate user preference records 320linked to user profile 202 through a userID 322 as a foreign key. Suchseparate preference records 320 can support any indication of userpreference including, for example, preferences for particular actors326, preferences for particular title 324, and indications of a user'sintensity of preference, encoded as preference Level 328. With respectto preference levels 328 in particular, the PVR can be programmed torecord a range of preference levels, for example, 1 through 10, in whicha preference level of ‘10’ indicates that the user likes a particularshow title very much, ‘5’ indicates neutrality, and a ‘1’ indicatesdislike. The Boolean field ‘Preference’ 278 on the show record 240indicates whether a recording is a preference recording. So that a usercan know what has been recorded on the user's behalf without the user'sprior knowledge, PVR screens showing a user's recorded shows typicallyindicate visually the recorded shows that are instances of preferencerecording.

The example show record of FIG. 3 includes data elements representing anidentification code 241 for the show represented by the show record, ashow title 241 a, a filename for the show 242, the genre of the show 243(comedy, drama, sports, and so on), an owner identification field called‘ownerID’ 244 recording the user ID of the user on behalf of whom theshow is recorded, the estimated storage space requirement for the show246, the duration of the show 247, a Boolean indication whether the showhas been viewed by the owner 248, an indication of the source of theshow 270, the schedule data for the show 272, a record period for theshow 274, and a retention period for the show 276.

Shows in the present example, however, are identified by identificationcodes 241, identification codes having no relationship to storagelocations in storage space. There would be, for example, oneidentification code for a show titled 241 a “Dukes of Hazzard,” anotheridentification code for the show titled 241 a “Star Trek,” and anotherfor the show titled 241 a “Buffy The Vampire Slayer.” Operating systems(154 on FIG. 2 a) generally organize storage space (166 on FIG. 2 a) insegments identified by filenames. Show records 240 according to FIG. 3therefore provide a filename field 242 to record the location in storagespace where a show is recorded so that shows can be located for viewingand later for deletion.

PVRs according to some embodiments of the present invention areprogrammed to utilize the ShowID field 241 as a completely unique keyidentifying a particular instance of a show to be recorded at aparticular date and time, encoded in the Schedule field 272 in FIG. 3.Other embodiments are programmed to treat the ShowID 241 as a shortidentifier for a title such as “Star Trek” or “Buffy The VampireSlayer.” In embodiments that treat the ShowID 241 are a titleidentifier, PVRs can build a unique key for a particular instance of ashow from the title 241 a plus the date and time (Schedule 272) when theshow is to be recorded.

The storage space requirement 246 and the duration 247 are related. Thestorage space requirement generally is expressed as some number ofbytes, kilobytes, or megabytes of storage space. The duration 247 isgenerally expressed in minutes or hours, a half-hour show, a two-hourmovie, and so on. Shows can be recorded in storage space using variouskinds of compression ranging from no compression to lossless compressionto quite lossy compression. For a show of a given duration, applyinghigher levels of compression reduces the storage space requirement forthe show.

The source 270 can be encoded to indicate a channel number for capturingrecorded content from broadcast television, cable television, orsatellite television. The source 270 can be encoded with an Internetaddress identifying a source for downloading recordable content.Internet addresses can be encoded by use of dotted decimal addresses,Universal Resource Locators (“URLs”), or Universal Resource Identifiers(“URIs”).

The schedule 272 is a data element for storing the broadcast schedule ofthe show represented by the show record 240. For example, the schedulefield 272 can be encoded with a date and time when a television show isbroadcast and therefore to be recorded. The record period 274 providesan indication of a period over which a show may be recorded many times.For example, schedule 272 can be encoded with a schedule indication ofWednesday, 7:00 p.m., and record period 274 can be encoded with ‘Januarythrough June,’ resulting in recording the indicated show weekly for sixmonths.

The retention period 276 is a field indicating how long to retain theshow before deleting it. The retention period 276 and indications ofviewing 248 can work together in various PVR according to embodiments ofthe present invention. In FIG. 3, for example, the PVR Profile 300includes a Boolean indication whether to delete shows only after theyare viewed, DeleteOnView 304. In a PVR according to FIG. 3, ifDeleteOnView 304 is set True, then the PVR will not delete a show fromstorage space until the show is viewed, even if the view time is laterthan the end of the retention period 276. The PVR will retain the showuntil the end of the retention period if the end of the retention periodis later than the time when the show is viewed. Alternatively,DeleteOnView 304 is reset False, then the PVR deletes the show at theend of the retention period regardless whether the show has been viewed.

The Viewed field 248 in the show records 240 indicates whether the ownerof the show has viewed the show. In a multi-user environment, however,it may be useful to retain the show in storage until more than one userhas viewed it. The viewing records 250 in FIG. 3 are an alternative oran expansion of the use of the Boolean Viewed field 248 in the showrecords 240 to allow more than one user to express an interest inviewing the show and retain the show in storage space until all usersindicating interest have viewed the show. The ShowID 252 is a foreignkey linking the viewing records 250 to a show record 240. The ViewerID254 is a user ID of a user indicating an interest in viewing the showidentified by the ShowID 252. Viewed 256 is a Boolean indication whetherthe user identified as ViewerID 254 has viewed the show. The fact that aviewing record 250 exists bearing a particular ViewerID 254 can betreated as an expression of interest, or a Boolean field such asInterest 258 can be added to viewing records 250 as an affirmativeexpression of interest in viewing the show identified in ShowID 252.

In lending and borrowing storage space among users, some method isneeded to keep track of who has lent what to whom. The example datastructures of FIG. 3 provide an example data structure, loan records230, for recording which lending user, identified by LenderID 232, haslent what amount of storage space 236, to which borrowing user,identified by BorrowerID 234. In a common example, a user identified bya userID in a user profile 202 shall have outstanding several loans ofstorage space, each represented by loan record 230. In such an example,the user's BorrowedSpace field 208 in the user's user profile 202 willcontain the sum of the amounts in the LoanAmount field 236 in therepresentative loan records 230.

FIG. 4 sets forth a flow chart depicting an exemplary method forautomated personal video recording 402. The method according to FIG. 4,described below also in terms of the example data structures of FIG. 3,is practiced upon a multi-user PVR having registered upon it amultiplicity of users, each user having allocated storage space on thePVR. Each user's allocated storage space includes storage space uponwhich shows are recorded (“used space”) as well as storage space uponwhich shows have not been recorded (“free space”). As shown in FIG. 4,the method comprises recording 402 for a user a show owned by the user.The user who owns the show, in slight anticipation, is referred to as a‘borrower.’ The borrower is a user registered on the PVR, that is, oneof the several users registered on the PVR.

The method according to FIG. 4 includes comparing 403 a borrower's freespace (206 in user profile 202 on FIG. 3) and the show's spacerequirement (246 in the show record 240). The comparison 403 supportsdetermining 404 whether the show's storage space requirement exceeds theborrower's free space. As shown in the example of FIG. 4, thedetermination whether storage space requirement exceeds free space isdone at the beginning of the overall recording process 402, that is,just prior to beginning actual recording, represented as step 410 onFIG. 4. If the show's storage space requirement does not exceed theborrower's free space, then recording continues to completion 410. Ifthe show's storage space requirement does exceed the borrower's freespace (the difference is referred to as ‘a deficit amount’), then a PVRimplementing the example method of FIG. 4 selects 406 a lender from whomto borrow some storage space.

A ‘lender’ in this sense is a user registered on the PVR having freestorage space or “free space,” that is, for example, a free storagespace field in the lender's user profile having as its value an amountlarger than zero and, reflected in the lender's user profile, free spacelarger than zero. All lenders may have MaximumLoan authorizations (226on FIG. 3) less than the deficit amount. All lenders may have free space(206 on FIG. 3) less than the deficit amount. It may therefore benecessary to borrow loan amounts from more than one lender, the loanamounts each being less than the deficit amount but adding up in totalto at least the deficit amount.

The PVR can fail to select one or more lenders having authorized andavailable storage space for lending. In such an eventuality, the PVR canbe programmed to stop 412 the recording of the show.

The example method of FIG. 4 includes borrowing 408 a loan amount from aselected lender. Borrowing the loan amount from the selected lender canbe carried out by use of the data structures of FIG. 3, for example, byadding the loan amount to the LoanedSpace field 210 in the lender's userprofile, subtracting the loan amount from the FreeSpace field 206 in thelender's user profile, and adding the loan amount to the BorrowedSpacefield 208 in the borrower's user profile. In addition to adjusting theLoanedSpace, FreeSpace, and BorrowedSpace as just described, in thisexample, the PVR also would create at least one loan record (230 on FIG.3) identifying the lender in LenderID 232, the borrower in BorrowID 234and the loan amount in LoanAmout 236. In this example, the borrowing iscarried out in dependence upon the deficit amount in the sense that theloan amount is the deficit amount.

In other examples, the loan amount, the amount actually borrowed is notequal to the deficit amount. The PVR may be programmed to borrow for theborrower more than the deficit amount, to give a little headroom forrecording. In addition, several loans may be required to amount to thedeficit amount, if, for example, no single lender has an authorizedmaximum larger than the deficit amount or if no single lender has freespace larger than the deficit amount. In such cases, there would be morethan one loan amount, none of which would be equal to the deficitamount, but the sum of which would be at least equal to the deficitamount. In these examples, although the loan amount may not be equal tothe deficit amount, the borrowing is carried out in dependence upon thedeficit amount in the sense that the deficit amount is a guide to thetotal amount to borrow, that is, a guide to borrowing the loan amount.

In the example method of FIG. 4, the owner of the show, that is, theborrower, or others who may be interested to do so, eventually view theshow. That is, the PVR displays the show 414. The loan amount of storagespace borrowed to support recording the show is then returned 416 to thelender. Returning 416 the loan amount involves effectively reversing theborrowing process. That is, the PVR finds each loan record bearing theShowID 241 of the recorded show. For each such loan record 230, the PVRsubtracts the LoanAmount 236 from the LoanedSpace field 210 in thelender's user profile, adds the LoanAmount 236 to the FreeSpace field206 in the lender's user profile, subtracts the LoanAmount 236 from theBorrowedSpace field 208 in the borrower's user profile, and deletes theloan record 230.

With reference to FIG. 5, and also with reference to the example datastructures of FIG. 3, we describe an exemplary method of selectinglenders. In selecting a lender, the PVR can, for example, as shown inFIG. 5, identify a lender by scanning 502 through lender authorizationrecords (like those depicted at reference 220 on FIG. 3) for MaximumLoanauthorizations (226 on FIG. 3) at least equal to the deficit amount. Tothe extent that the PVR supports borrowerIDs 224 in lendingauthorization records 220, then the scan is for lender authorizationsrecords authorizing, for the user who owns the show to be recorded, aMaximumLoan amount 226 at least equal to the deficit amount. To theextent that the PVR supports borrowerIDs 224 with wild cardauthorizations for lending to any user, then the scan is for lenderauthorizations records authorizing lending to the user who owns the showto be recorded, or to any user, a MaximumLoan amount 226 at least equalto the deficit amount. Using the LenderID 222 in the scanned lendingauthorization records as a foreign key into the user profiles 202, thePVR compares MaximumLoan authorizations 226 and the free space 206 foruser identified as lenders in lending authorization records havingMaximumLoan amounts 226 at least equal to the deficit amount. The PVRthen selects as the lender the first lender found in the scan andcomparison having a MaximumLoan amount 226 and a free space amount 206both of which are at least equal to the deficit amount. In this sense,lenders are selected in dependence upon the deficit amount.

All lenders may have MaximumLoan authorizations (226 on FIG. 3) lessthan the deficit amount. All lenders may have free space (206 on FIG. 3)less than the deficit amount. It may therefore be necessary to borrowloan amounts from more than one lender, the loan amounts each being lessthan the deficit amount but adding up in total to at least the deficitamount.

FIG. 6 depicts a method of selecting lenders for multiple loans whoseindividual loan amounts add up to a total loan amount at least equal tothe deficit amount. In particular, the example method depicted in FIG. 6includes scanning 508 lending authorization records (220 on FIG. 3) ‘forthe borrower,’ meaning scanning lending authorization records fromvarious lenders to find the ones that authorize loans to the currentborrower, that is, having the borrower's user ID in the BorrowerID field224. To find lenders who authorize lending to the borrower (or possiblyto any borrower, with wild card authorizations as described above) andalso have at least some free space, the method of FIG. 6 compares 510MaximumLoan 226 values from the lending authorization records with thefree space values 206 in the corresponding user profiles 202. Because inthis example, no single lender alone has sufficient free space to meetthe deficit, the example method also, upon finding a lender who has somefree space, creates 512 a loan record 230 having a LoanAmount 236 equalto the lender's MaximumLoan amount 226 or the lender's free space 204,whichever is less. The example method also adds 514 the loan amount tothe borrower's BorrowedSpace 208, adds 516 the loan amount to thelender's LoanedSpace 210, subtracts 518 the loan amount from thelender's FreeSpace 206. The example method adds 520 the loan amount to arunning total for the current show, and the example repeats 522 thesteps of scanning 508, comparing 510, creating loan records 512,accounting for the loans (514, 516, 518), and adding a running total520, until the running total of the loan amounts is at least equal tothe deficit amount.

In the example method of FIG. 6, it is the existence of a lendingauthorization record bearing the borrower's user ID in the BorrowerIDfield 234 that represents authorization for a loan from a lender (thelender identified in the LenderID field 222) to the borrower. The PVRprogrammed to find, and finding or not finding at least one such lendingauthorization record, is determining whether there are lendersauthorizing borrowing. More particularly, the PVR programmed to find,and finding or not finding at least one such lending authorizationrecord, is determining whether the borrower is authorized to borrow fromone or more lenders. The example method of FIG. 6 selects as lenders oneor more users whose free space is at least equal to the deficit amount.

FIG. 7, viewed in light of the example data structures of FIG. 3,depicts an alternative exemplary method of selecting lenders, similaroverall to the example method of FIG. 6, but dependent also uponpriorities. As shown in FIG. 3, PVRs implemented as embodiments of thepresent invention can include lending priority ratings 214 in userprofiles 202. In the method of FIG. 7, each user has a priority ratingand selecting a lender comprises selecting, in dependence upon thepriority ratings, lenders whose free space is at least equal to thedeficit amount. If a single lender can be found whose free space is atleast equal to the deficit amount, then only the single lender isneeded. If the first lender satisfying priority dependence hasinsufficient free space to meet the deficit, the PVR can be programmedeither to make more than one loan or to continue looking for a singlelender with sufficient free space. If no single lender can be found withsufficient free space to meet the deficit, then the PVR is typicallyprogrammed to make more than one loan.

More particularly, with regard to FIG. 7, the example method depictedincludes finding 802 a lending authorization record (220 on FIG. 3) ‘forthe borrower,’ meaning a lending authorization record having theborrower's user ID in the BorrowerID field 224. The method of FIG. 6compares 804 the MaximumLoan 226 value from the lending authorizationrecord with the free space value 206 in the corresponding user profile202, that is, in the user profile of the lender identified in theLenderID field 222 in the lending authorization record 220.

The method of FIG. 7 includes checking for correct priority 806. Thecorrect priority depends on the particular PVR. The PVR can beprogrammed, for example, so that the priority borrower's priority mustbe higher than the lender's priority, greater that or equal to thelender's priority, less than the lender's priority, or less than orequal to the lender's priority. Other ways of programming a PVR forpriority comparisons or dependencies will occur to those of skill in theart, and all such ways are well within the scope of the presentinvention. In the method of FIG. 7, if the lender identified in alending authorization record fails the priority requirement, the methodloops back and repeats the process of the method by finding anotherlending authorization record 802.

In operation of the example method of FIG. 7, it is possible that nosingle lender alone has sufficient free space to meet the deficit. ThePVR implementing the method of FIG. 7, therefore is programmed so that,upon finding a lender who has some free space and meets the priorityrequirement, the PVR creates 808 a loan record 230 having a LoanAmount236 equal to the lender's MaximumLoan amount 226 or the lender's freespace 204, whichever is less. The example method of FIG. 7 also adds 810the loan amount to the borrower's BorrowedSpace 208, adds 812 the loanamount to the lender's LoanedSpace 210, and subtracts 814 the loanamount from the lender's FreeSpace 206. The example method adds 816 theloan amount to a running total for the current show, and the examplerepeats 818 the steps of finding an lending authorization record 802,comparing 804, checking priority 806, creating loan records 808,accounting for the loan (810, 812, 814), and adding a running total 816,until the running total of the loan amounts is at least equal to thedeficit amount.

FIG. 8 depicts an alternative exemplary method of selecting lenders.More particularly, the example method of FIG. 8 selects a lender who,among all users having free space at least equal to the deficit amount,has the highest ratio of free space to allocated storage space. Theexample method of FIG. 8 is based upon the lending authorizationgranularity of the lending authorization 220 records in FIG. 3, that is,lending authorizations from a lender 222 to a borrower 224 of aparticular maximum amount 226. The example method of FIG. 8 begins byfinding 702 a first lending authorization record 220 authorizing lendingto the borrower 224 from a lender whose FreeSpace 206 is at least equalto the deficit. The method of FIG. 8 then retains in temporary storagethat first LenderID and the ratio of that lender's FreeSpace 206 to thedeficit amount. The method then includes repeatedly 710 scanning 706 ina loop through the remaining lending authorization records for theborrower, comparing 708, for each lender authorizing lending to theborrower and having FreeSpace at least equal to the deficit, thelender's ratio of free space to the deficit amount with the ratiocurrently retained in temporary storage, and retaining 709 in temporarystorage the highest ratio and the user ID of the lender having thehighest ratio. The user ID retained in temporary storage at the end ofthe loop is identified 712 as the lender for the current loan. The loanis completed by adding 714 the loan amount to the borrower'sBorrowedSpace 208, adding 716 the loan amount to the lender'sLoanedSpace 210, and subtracting 718 the loan amount from the lender'sFreeSpace 206.

Processing of borrowed storage space according to embodiments of thepresent invention includes returning borrowed space to lenders. Asdescribed earlier, return of borrowed space can occur when the borrowerhas viewed the show for which the space was borrowed. It can also occur,however, within the scope of the present invention, that borrowed spaceneeds to be “repossessed” by a lender. More particularly, when recordinga show for a lender, the show can have a storage space requirementexceeding the lender's free space. The difference between the storagespace requirement of the show and the lender's free space is called a‘deficit amount.’

The lender in this example is a user who has already loaned some storagespace to one or more other users, that is, borrowers. In this example, aPVR according to an embodiment of the present invention is programmed todetermine whether other free space is available for lending from otherusers to the lender, and, if no other free space is available forlending to the lender, returning from at least one borrower to thelender at least part of the loan amount previously loaned to theborrower from the lender.

FIG. 9, viewed in conjunction with the example data structures of FIG.3, depicts an example of a method for returning borrowed storage spaceto the lender from whom it was borrowed. The method of FIG. 9 begins 802with a scheduled recording of a show having a storage space requirementexceeding the free space of the user who scheduled the recording, the‘owner’ of the show. In this example, the owner is a lender. That is,the owner of the show to be recorded has outstanding loans of storagespace to one or more users, loans represented by loan records of thekind illustrated at reference 230 on FIG. 3. In this example, the lenderhas a deficit. That is, the lender's FreeSpace amount 206 in thelender's user profile 202 is less than (by a deficit amount) theSpaceRequirement 246 in the show record 240 representing the show to berecorded.

The PVR in this example is programmed to scan lending authorizationrecords to determine whether there exists storage space available forthe lender to borrow 804. If storage space is available for the lenderto borrow, then the PVR arranges a loan to the lender 816, and recordingcontinues 822. In this example, if there is no space available forborrowing, then the PVR repossesses at least some of the storage spacepreviously borrowed by other users (“borrowers”) from the lender. Moreparticularly, the PVR proceeds by finding 806 a loan record 230representing a loan of storage space from the lender to a borrower,adding 808 the LoanAmount 236 from the loan record to the lender'sFreeSpace field 206, subtracting 810 the LoanAmount 236 from thelender's LoanedSpace field, and subtracting 811 the LoanAmount 236 fromthe borrower's BorrowedSpace field.

In the example of FIG. 9, there remains the problem of whether theborrower gets to keep the borrower's show, the show identified in theShowID 241 in the loan record 230, the show for which the borrowerpreviously borrowed storage space from the lender. In the example ofFIG. 9, the PVR is programmed to determine whether the borrower hassufficient free space 206 to store the show identified in the ShowIDfield 241 in the loan record 230. If not, the PVR deletes the borrower'sshow 818, deletes the loan record 230, and completes the recording 822.If the borrower does have sufficient free space to accommodate theborrower's show, the PVR subtracts 820 the loan amount from theborrower's FreeSpace 206, deletes 812 the loan record 230, and completesthe recording 822.

If the LoanAmount in the loan record is less than the deficit amount,the PVR may be programmed to repeat 824 the steps of finding a loanrecord 806, repossessing loaned storage space (808, 810, 811), deletinga borrower's show 820 or subtracting a loan amount from borrower'sFreeSpace 818, and deleting a loan record 812, until sufficient storagespace has been repossessed to support completing the recording of thelender's show 822. This is an example of repossessing more than one loanamount. That is, in this example, when the lender has outstanding loanamounts to more than one borrower, or more than one loan to the sameborrower, wherein returning from the borrower to the lender at leastpart of the loan amount includes returning at least parts of loanamounts from more than one borrower.

Compression Levels and Rechecking Storage Space Requirements

The storage space requirement 246 for a show 240 is an estimatecalculated on the basis of the duration 247 of the show and theestimated compression level for the show. FIG. 3 illustrates threeexample data structures for compression level: One as a defaultcompression level 308 for the entire PVR 300, another as a defaultcompression level 261 at the user level 202, and a third as acompression level 279 for particular show 240. The default compressionlevels at the user level 261 and the PVR level 308 are provided so thatthe PVR can record a compression level 279 in a show record 240 whenevera show record is created, either by a user's scheduling a show forrecording or by preference recording.

As an aid to understanding, we discuss an example of a calculation of adesired minimum compression level. As mentioned earlier, one of theformats defined for HDTV broadcasting within the United States is 1920pixels horizontally by 1080 lines vertically, at 30 frames per second.If these numbers are all multiplied together, along with 8 bits for eachof the three primary colors, the total data rate required would beapproximately 1.5 gigabits per second. Because of the 6 megahertzchannel bandwidth allocated for HDTV, each channel will only support adata rate of 19.2 Mb/sec, which is further reduced to 18 Mb/sec by thefact that the channel must also support audio, transport, and ancillarydata information. This restriction in data rate means that the originalsignal must be compressed by a figure of approximately 83:1. Thisestimated minimum compression is for broadcast only, with commercialHDTV quality of frame rate and resolution. In addition, this estimatedminimum compression is raw broadcast compression only, just enough tofit a video stream into a transmission bandwidth, not yet affected bydesirable further (relative) compression needed to fit a show into aparticular space requirement in the storage space of a PVR. Asillustrated by the example compression level records in FIGS. 10 a and10 b, discussed in more detail below, users willing to reduce videoquality can achieve much higher compression levels for data storage.

As a further aid to understanding compression operations in PVRs, wepresent an example calculation of a compression ratio, presented interms of a single image, which could be, for example, a static graphicimage or a single video frame. The compression ratio is defined forcalculation as the number of bits/pixel in the original image divided bythe number of bits/pixel in the compressed image. Assume that theoriginal image has a resolution, or rather a size, of 320×240 pixelseach represented in a 24-bit data word. And assume that after initialcompression the compressed file size is 5000 bytes. Then the bits/pixelfor the compressed image is (5000*8)÷(320*240)=0.52 bits/pixel. In otherwords, the original image used need 24 bits to represent each pixel, butafter compression, only need 0.52 bits are used to store each pixel (onaverage). The compression ratio therefore is 24÷0.52=46.

Factors that affect overall estimate compression level are shown intables 420 and 602 in FIGS. 10 a and 10 b. As shown in both tables, butreferenced to table 420, factors affecting compression level are shownto include encoding type 424, which we assume carries with it aparticular compression algorithm; supported colorspace size 426, framerate 428, resolution 430, and audio quality 432.

The example records in table 420 show several examples of compressionlevel 422 estimated on the basis of the factors affecting compression.The compression levels are shown in absolute terms and then inparenthesis relative to a video source bit stream. Table 420 isorganized with respect to an HDTV source having an initial resolution430 of 1930×1080. Table 602 is organized with respect to an NTSC sourcehaving an initial resolution of 720×480.

Record 440 shows an estimated initial raw compression level 422 in thesource stream of 80:1 estimated on the basis of encoding according toMPEG-2, colorspace size 4:4:4 or ‘48,’ frame rate 428 of 30frames/second, resolution of 1930×1080 pixels (an HDTV standard), with‘High’ audio quality 432. Record 440 is shown with a relativecompression of (1) with respect to itself.

The target records, records 442 through 450, illustrated compressionlevels supported by an exemplary PVR with respect to a video source ofthe kind represented in the source record 440. Record 442, for example,shows an estimated absolute compression level 422 of 480:1, or acompression level of (4) relative to the source stream, estimated on thebasis of encoding according to MPEG-2, colorspace size ‘48,’ frame rate428 of 30 frames/second, resolution of 720×480 pixels (an NTSC videostandard), with ‘High’ audio quality 432. In other words, recompressingthe source stream using a resolution reduced from 1930×1080 (HDTV) to720×480 (a high quality of NTSC video) reduced projected spacerequirement for a subject show by a factor of six. This is a usefuldemonstration of the fact that, although algorithmic compression alonecan result in absolute compression ratios in the range of approximately100 to 200, reductions in parameters other than compression technique assuch, factors such as, for example, colorspace, frame rate, resolution,and audio quality, can result in very large overall compression levels.

Record 444 shows an estimated absolute compression level 422 of 960:1and a relative compression of (12) with respect to the source stream,achieved by reducing the size of the colorspace 426 from 48 to 24, thatis, for example, from 4:4:4 to 4:2:4. Record 446 shows an increase inrelative compression to approximately (48) through an additionalreduction in resolution 430. Record 448 shows an estimated relativecompression level of (100) from changing encoding 424 to MPEG-1 andreducing audio quality 432. Record 450 shows an estimated relativecompression level (140) estimated from an additional change in encoding424 to MJPEG and an additional reduction in audio quality 432.

For a further example, consider table 602 in FIG. 10 b. Table 602 showsa video source 604 having raw compression of 80, encoded 424 in MPEG-2,supported a colorspace size 426 of 48 (4:4:4), having a frame rate 428of 30, a resolution 430 of 720×480, and high audio quality 432. Therelative target compressions supported in a example PVR implementingtable 602 include those represented by record 606, having a relativecompression level of 4, achieved by reducing resolution 430; record 608,having a relative compression level of 16, achieved by a furtherreduction in resolution 430; record 610, having a relative compressionlevel of 32, achieved by reducing colorspace 426; record 612, having arelative compression level of 128, achieved by changing encoding 424 andreducing audio quality 432; record 614, having a relative compressionlevel of 256, achieved by a further change in encoding 424 and a furtherreduction in audio quality 432.

The examples records representing various compression levels in FIG. 10a and 10 b illustrate that compression level generally increases withdecreases in colorspace size, resolution, and audio quality. Compressionlevel also increases with decreases in frame rate. Effect on compressionlevel of different encoding types with their associated compressionalgorithms depends on the particular encoding type and the kind ofcontrol provided by particular codecs implementing an encoding. For allthese reasons, representations of compression level in variousembodiments of the present invention typically are estimates based uponthe factors discussed, and other factors as will occur to those of skillin the art. The use of a wide variety of video encodings, videocompression algorithms, and factors affecting video compression levels,as will occur to those of skill in the art, are all well within thescope of the present invention.

Tables such as those shown in FIG. 10 a and 10 b can be used toestablish a show's storage space requirement. A show will have a rawcompressed file size or space requirement determined, for a show of agiven duration, on the basis of a source record such as the exemplaryones depicted at references 440 and 604. PVRs according to embodimentsof the present invention can support establishment at their systemlevels in, for example, a PVR profile such as the one depicted atreference 300 in FIG. 3, a data element, as TargetFileSize 316, in whichis stored a storage space guideline for all shows recorded on the PVR.To accommodate shows of varying length, the TargetFileSize 316 parametercan be expressed in terms of, for example, megabytes per minute, so thatshows having durations of 60 minutes would have target storagerequirements twice as large as 30 minute shows, and so on. Then, givenan initial raw compressed file size based on source parameters (440,604) exceeding a show's target space requirement according toTargetFileSize 316, a PVR can be programmed to scan a table such asthose depicted in FIG. 10 a and 10 b to find a relative compressionlevel and parameter set whose additional compress will result in anactual space requirement no greater than the target space requirementaccording to TargetFileSize 316.

For example, consider given a 30 minute NTSC show broadcast in MPEG-2with a resolution of 720×480 requiring with no further compression aninitial raw compressed file size of 50 megabytes, corresponding to asupported video source depicted at record 604 in table 602 on FIG. 10 b.In this example, the TargetFileSize 316 indication for a 30 minute showis 15 megabytes. The PVR is programmed to scan through table 602 for asupported compression configuration resulting in a file size no greaterthan 15 megabytes. The PVR selects the supported compression levelrepresented by record 606, having a relative compression level of 4 withrespect to source video. The PVR orders its MPEG-2 codec to recompressthe show using the parameters of compression level record 606, resultingin an actual (estimated) storage requirement of 12.5 megabytes which thePVR stores as the show's storage requirement in, for example, aSpaceRequirement data element 246 in a representative show record 240 asdepicted on FIG. 3.

The tables in FIGS. 10 a and 10 b show two example configurations ofsupported compression levels in PVRs according to embodiments of thepresent invention. Many such configurations are possible, including atleast one for each kind of source video supported by any particularembodiment of PVR. All such configurations as will occur to those ofskill in the art are well within the scope of the present invention.

Shows recorded on PVRs generally are compressed, but the actual level ofcompression actually achieved generally is known only as an estimate.Each show's storage space requirement, therefore, is an estimate. Inother words, when a PVR begins recording a show, perhaps even borrowingstorage space in dependence upon a comparison of the show's storagerequirement and a user's free space, the PVR cannot know for certainthat the amount of space borrowed can actually support the recording. Amethod is needed for checking the show's storage space requirementduring recording and borrowing more space if needed. In fact, wedisclose two ways of administering the risk of storage space estimation,one method using a space check threshold for checking a show's storagespace requirement during recording and a second method usingoverallocation.

FIG. 11, with reference to the example data structures in FIG. 3,depicts an exemplary method of checking a storage space requirementduring recording. As such, the method described with reference to FIG.11 is an expansion of the recording step (410 on FIG. 4) describedearlier. As shown in FIG. 11, the method includes tracking 452 therecording period and the actual storage space used during actualrecording. The tracked recording period is a space check threshold 310multiplied by the show's duration 247.

The space check threshold 310 is the portion of the show duration (247in show record 240) to be recorded before recalculating the show'sstorage space requirement 246. The space check threshold can beimplemented in data structures as shown at reference 310 in the PVRprofile structure 300 in FIG. 3. A show having, for example, a duration247 of 30 minutes in a PVR having a space check threshold of 90%, thetracked recording period for the show would be 27 minutes.

When the tracked recording period is at least equal to the space checkthreshold 310 multiplied by the show's duration 247, the PVR checks theestimated storage space requirement by comparing the actual storagespace used with the amount of storage space projected to be used basedon the estimated storage space requirement. The projected usage is thespace check threshold 310 multiplied by the original estimated storagespace requirement 247.

If the actual space used is greater than the projected usage, the PVRaccording to the method of FIG. 11 increments the show's storage spacerequirement 457. Incrementing the show's storage space requirement canbe accomplished by adding a predetermined proportion of the originalstorage space requirement. A predetermined proportion can be stored as,for example the SpaceCheckAddProportion 312 in the PVR profile 300. Ifthe original storage requirement for the show reflected in field 246 inthe show record 240 were 20 megabytes, and the SpaceCheckAddProportionwere 10%, then the PVR would add 2 megabytes to the show's storage spacerequirement 246, resulting in a new storage space requirement of 22megabytes.

The method of FIG. 11 includes comparing the borrower's free space andthe new storage space requirement to determine whether a deficit exists.This comparison is useful now because, even if the user had a deficitrequiring borrowing when recording began, whether the user has a deficitnow is not known. The borrower's free space can change after recordingbegins. If a deficit does exist 460, then the method of FIG. 11 selectsa lender 462, borrows a new loan amount 466 at least as large as thecurrent deficit, and completes the recording 468. If the PVR accordingto FIG. 11 is unable to find a lender, recording stops 464.

Assume that the initial bit rate for a 30 minutes show, a video downloadfor example, is 150 kilobits/second, which would be fairly high qualityvideo at MPEG-1. Thirty minutes is 1800 seconds, the duration of theshow. 150,000 multiplied by 1800 is 270 megabits total spacerequirement, divided by 8 bits/byte is about 34 megabytes for the show'sstorage space requirement. This show is downloaded with quite a lot ofcompression, and the storage space requirement is definitely anestimate.

Because we know before beginning recording that the storage spacerequirement is an estimate, another way of dealing with the risk ofestimation is shown in the method illustrated in FIG. 12. We discuss themethod of FIG. 12 in view of the example data structures of FIG. 3. Themethod according to FIG. 12 begins the overall recording process byincrementing the show's storage space requirement in accordance with anoverallocation rate. The overallocation rate in this example is providedin the data structures of FIG. 3 at reference 314 in the PVR profile300. If the overallocation rate 314 were 110%, for example, thenaccording to the method of FIG. 12, the show's storage space requirementwould be increased from 34 megabytes to 37.4 megabytes (34*110%).

The method of FIG. 12 continues by comparing the borrower's free spaceand the show's (new) storage space requirement 458, selecting a lenderif a deficit exists 462, borrowing a loan amount 466, and completing therecording 468. The method of FIG. 12 proceeds after recording to comparethe actual storage space used (read from an operating system's filesystem, for example, using the show's filename 242) and return to alender the unused amount.

Returning the unused loan amount 474, expressed in terms of the datastructures of FIG. 3, includes finding a loan record 230 bearing theShowID 241 of the recorded show 240. The PVR according to the method ofFIG. 12 subtracts the unused amount of storage space from theLoanedSpace field 210 in the lender's user profile, adds the unusedamount to the FreeSpace field 206 in the lender's user profile, andsubtracts the unused amount from the BorrowedSpace field 208 in theborrower's user profile.

The effectiveness of compression depends on genre. More particularly,the effectiveness of actual video compression depends on the motion ofthe subjects depicted in the video. Consider five frames of a close-upstill life of an apple. The first frame must be encoded in its entirety,but the subsequent four frames need only refer to the first frame; theyneed not be encoded at all. In five frames of video tightly focused oneleven football players during a play, however, a large proportion ofthe pixels in the frame will change from frame to frame for each of thefive frames. Five frames of football is must less effectively compressedthan five frames of a fine arts show. The arts are more effectivelycompressed than drama. Drama is more effectively compressed than actionmovies. Action movies are more effectively compressed than sportsevents, and so on.

The methods of FIGS. 11 and 12 are also adapted to address the problemthat effectiveness of compression varies with genre. First we discussthe method of FIG. 12 in view of the example data structures in FIG. 13.FIG. 13 depicts a form of PVR profile 300, already familiar from FIG. 3,which has been amended to shift to a new space check profile 350 thespace checking fields SpaceCheckThreshold 310, SpacecheckAddProportion312, and OverallocateRate 413. The new space check profile 350 includesa genre field 316. The space check profile 350 is useful to vary,according to genre 316, the values of the space checking fieldsSpaceCheckThreshold 310, SpacecheckAddProportion 312, andOverallocateRate 413.

In a PVR implementing the method of FIG. 11 for checking storage spacerequirements during recording, the SpaceCheckAddProportion 312 can beset in a space check profile 350 to 5% for a genre 316 of ‘fine arts.’The SpaceCheckAddProportion 312 can be set in another space checkprofile to 10% for a genre 316 of ‘drama.’ The SpaceCheckAddProportion312 can be set in still another space check profile to 15% for a genre316 of ‘action.’ The SpaceCheckAddProportion 312 can be set in yetanother space check profile to 20% for a genre 316 of ‘sports.’ And soon, using different increments for various genres as will occur to thoseof skill in the art or as set in the discretion of users authorized toset the SpacecheckAddProportion in space check profiles.

In a PVR implementing the method of FIG. 12 for overallocating storagespace at the beginning of the recording process, the proportionalincrement of overallocation, the OverAllocationRate 314, can be set in aspace check profile 350 to 105% for a genre 316 of ‘fine arts.’ TheOverAllocationRate 314 can be set in another space check profile to 110%for a genre 316 of ‘drama.’ The OverAllocationRate 314 can be set instill another space check profile to 115% for a genre 316 of ‘action.’The OverAllocationRate 314 can be set in yet another space check profileto 120% for a genre 316 of ‘sports.’ And so on, using differentOverAllocationRate values for various genres as will occur to those ofskill in the art or as set in the discretion of users authorized to setthe SpacecheckAddProportion in space check profiles.

With reference to FIG. 14 and in view of the data structures of FIGS. 3and 13, we described a method of incrementing the storage spacerequirement in dependence upon genre. More particularly, the method ofFIG. 14 is a more detailed method of incrementing the storagerequirement as disclosed in connection with reference 457 of FIG. 11, amethod of checking a storage space requirement during recording. Themethod of FIG. 14 includes reading 1402 the show's genre (243 on FIG. 3)from the show record 240, selecting 1404 a space check profile 350 independence upon the show's genre, and incrementing 1406 the storagespace requirement by the product of the SpaceCheckAddProportion (312 onSpace Check Profile 350 in FIG. 13) and the current SpaceRequirement forthe show (246 in show record 240 on FIG. 3).

With reference to FIG. 15 and in view of the data structures of FIGS. 3and 13, we described a method of overallocating storage space at thebeginning of the recording process. More particularly, the method ofFIG. 15 is a more detailed method of incrementing a storage spacerequirement according to an overallocation rate as disclosed inconnection with reference 470 of FIG. 12. The method of FIG. 15 includesreading the show's genre (243 on FIG. 3) from the show record 240,selecting a space check profile 350 in dependence upon the show's genre,and incrementing the storage space requirement to the amount of theproduct of the OverAllocateRate (314 on Space Check Profile 350 in FIG.13) and the current SpaceRequirement for the show (246 in show record240 on FIG. 3).

Pools and Groups

At this point we have disclosed at length personal video recording withloans of storage space among users. We can add power and flexibility topersonal video recording, however, by supporting various ways ofallowing users to aggregate their abilities to lend, borrow, and recordshows. We therefore now turn our attention to pools and groups.

We begin with a reconsideration of overall structure of storage space.With reference to FIG. 2 b, we described above an overall structure ofstorage space in which all available storage space was allocated tousers. Now with reference to FIG. 16, we describe a more flexibleoverall structure of storage space. The exemplary structure of storagespace according to FIG. 16 depicts, at reference 1802, 20% of theoverall storage space as unallocated to anyone; at reference 1810, 20%allocated to Father; at reference 1808, 20% to Mother, at reference1806, 10% to a group, at reference 1804, 10% to a pool; at reference1814, 10% to Son; and at reference 1812, 10% to Daughter. In thefollowing discussion we describe in some detail how this new overallstructure of storage space adds flexibility to personal video recording.

Pools

A pool is an aggregation of storage space for lending. Pools areassigned their own storage space. Pools lend their storage space toborrowers. Although there is nothing within the scope of the presentinvention that excludes pools from lending, in this disclosure, ourexamples of aggregations for borrowing are the ‘groups’ described below.In our examples of pooling, to reduce the risk of confusion and augmentclarity of explanation and understanding, we describe examples of poolsthat do not borrow.

Pools acquire their storage space by assignments of storage space fromunassigned storage space or through allocations from users' free space.Pools are generally authorized to lend their storage space to users orto groups. An example of an authorization to lend is creations of alending authorization record.

More particularly, FIG. 20 depicts example data structures useful forimplementation of pools. The data structures for lending authorizationrecords 220, loan records 230, and the PVR profile 300 are similar tothose of FIG. 3. PVRs according to this kind of embodiments contain atleast one pool profile 2002, each pool profile representing a pool. Thepool profile 2002 comprises the data elements PoolID 2004, a poolidentification field; AllocatedSpace 198 in which is stored the amountof storage space currently allocated to the pool; FreeSpace 206 in whichis stored the portion of the pool's allocated space available forrecording or lending; and LoandedSpace 210 in which is stored the amountof space currently on loan from the pool to users or groups.

Loans of storage space from a pool are authorized in lendingauthorization records such as those depicted at reference 220. Thelending authorization records comprise the data elements LenderID 222.In the case of loan authorizations from pools, the LenderID field storesa pool ID. Fields of the lending authorization records also include aBorrowerID 224, which stores a user ID or a group ID of a user or groupauthorized to borrow from the pool. The BorrowerID field 224 can alsostore a wild card value such as a ‘*,’ indicating authorization to lendfrom the pool to any user or group. Fields of the lending authorizationrecords also include a MaximumLoan field 226 in which is stored themaximum amount of storage space authorized by the lending authorizationrecord for lending from the pool to a borrower.

FIG. 17 sets forth a flow chart depicting a method for automatedpersonal video recording with pools in which the method includesselecting 1510 a lender from among one or more lenders 1502. The lenderscomprise at least one user 1504 having free storage space and at leastone pool 1506 having free storage space. Selecting a lender in themethod of FIG. 17 is carried out in dependence upon a deficit amount1512. The deficit amount is the amount by which a show's storage spacerequirement exceeds a borrower's free space. The borrower is the user orgroup on whose behalf a show is to be recorded.

The selecting is carried out in dependence upon the deficit amount 1512.That is, for example, a lender is selected who has authorized lending ofat least the deficit amount and who has free space at least equal to thedeficit amount. Alternatively, if no single lender has sufficient freespace and sufficient lending authorized, several lenders may beselected, until the lenders' aggregate free space and maximum loanamount authorizing lending to the borrower are at least equal to thedeficit amount.

The method according to FIG. 17 includes borrowing 408, in dependenceupon the deficit amount 1512, from the selected lender 1508 for aborrower 1514, at least one loan amount of storage space, the borrower1514 having allocated storage space 1516 on the PVR optionally includingfree space 1518. The borrowing is carried out in dependence upon thedeficit amount in that at least the deficit amount needs to be borrowed.The loan amount may be for more than the deficit amount. The PVR can beprogrammed to build up the loan amount from several loan amounts each ofwhich is less than the deficit amount but the sum of which is at leastthe deficit amount. When the loan, or loans, is settled 408, a PVRprogrammed according to FIG. 17 proceeds to record 1520 a show for theborrower. In this example, the show has a storage space requirement (asreference 246 on FIG. 3) exceeding the borrower's free space (reference206) by the deficit amount 1512.

In the method according to FIG. 17, the selected lender 1508 can be apool 1506. In the method according to FIG. 17, the borrower can be auser. As discussed in more detail below, the borrower also can be agroup. The method of FIG. 17, as described in more detail below, caninclude creating 1522 a pool, including assigning 1524 storage space tothe pool.

More particularly, FIG. 18 sets forth a flow chart depicting anexemplary method of assigning storage space to a pool. In the method ofFIG. 18, assigning 1524 storage space to the pool 1506 comprisesallocating 1612 storage space from at least one user 1604 to the pool1506. It is useful for the user to have free space 1606 available forallocation to the pool. In the method of FIG. 18, allocating storagespace 1612 to the pool 1506 includes decrementing 1616, by a pooledallocation amount 1618, the user's storage space allocation 1604 and theuser's free space 1606. The method of FIG. 18 also includes incrementing1614, by the pooled allocation amount 1618, the pool's free space 1610and the pool's allocated space 1608.

FIG. 19 sets forth a flow chart depicting an alternative exemplarymethod of assigning storage space 1524 to a pool 1506. The method ofclaim 19 includes assigning a pooled allocation amount 1704 of storagespace directly from unallocated storage space 1702 to the pool 1506. Inthe method of claim 19, assigning 1524 a pooled allocation amount to thepool includes incrementing 1706, by the pooled allocation amount 1704,the pool's free space 1610 and the pool's allocated space 1608.

Now with respect to the overall storage space structures illustrated inFIGS. 2 b and 16, consider the increased flexibility afforded by the useof pools. In the overall structure according to FIG. 16, for example,parents (1808, 1810) can treat the pool 1804 as a repository ofborrowing overhead for the children (1814, 1812). By issuing lendingauthorization records authorizing lending from the pool to the children,with no lending authorization records authorizing lending directly fromthe parents to the children, the parents empower the children withavailable storage space beyond that allocated specifically to thechildren, and, at the same time, reserve for the parents'exclusive useof their own core allocations (1808, 1810).

Groups

Groups are aggregations of recording power. That is, groups aggregatefree space and borrowing power in support of recording rather thanlending. Although it is not a limitation of the present invention, inour exemplary aggregations, it is groups rather than pools that areauthorized to borrow storage space. It is pools rather than groups, inour examples, that lend storage space. Groups comprise members, andgroups, at least implicitly and as described in more detail below,apportion storage space among their members.

Group space, that is, storage space assigned to a group, can beallocated or borrowed. Group space can be allocated from users' freespace or from unallocated space. Group space can be borrowed from anylender issuing a lending authorization record in favor of a group, thatis, from users or pools.

FIG. 21 a depicts example data structures useful for representing groupsin PVRs according to various embodiments of the present invention. Agroup profile 2102 represents a group. Group profiles typically have agroup identification field such as GroupID 2104. The group profile 2102also provides data elements for allocated space 2130, free space 2132,used space 2134, borrowed space 2136, content restrictions 2138 onrecordable content allowed for the group, and a default compressionlevel 2140 at the group level 2102.

The exemplary data structures of FIG. 21 a provide a member record 2106representing each member of a group. A member of a group is a userhaving a member record identifying the user as a member of a group. Themember records 2106 contain a group ID field 2104 as a foreign keylinking each member record to a group in a one-to-many relationship.

The member records 2106 contain a user ID field 322 identifying a useras a member of the group identified in the GroupID field 2104. The userID field 322 is a foreign key linking the member records one-to-many touser profiles 202. In the exemplary data structures of FIG. 21 a,therefore, member records implement a many-to-many relationship betweengroups 2102 and users 202. That is, each group can have many users asmembers, and each user can be a member of many groups.

Groups can have stated preferences. More particularly, groups, throughtheir authorized representatives, can create expressions of preferencein the form, for example, of user preference records 320. For groups'expressions of preference, the UserID field 322 in a preference record320 stores a group ID, acting as a foreign key, linking user preferencerecords 320 one-to-many to groups. That is, each group can assert manypreferences. PVRs according to embodiments of this kind are programmedto carry out preference recording for groups in the same way thatpreference recording is done for individual users.

Groups' authorized representatives can schedule recordings of shows forgroups in the same way that shows are scheduled for users, for example,by creation of a show record effected through a user interface. Moreparticularly, a show 240 scheduled to be recorded on behalf of a group2102 has stored in its OwnerID field 244 the group ID of the group onwhose behalf the show is scheduled to be recorded. In such embodiments,that group is considered the owner of such a show.

As for borrowing, any lending authorization record (220 on FIGS. 3 and20) issued by any lender can store in its BorrowID field 224 a group ID,effectively authorizing lending to a group. Groups are authorized toborrow by use of a ‘*’ wild card such as a ‘*’ in the BorrowerID field224 when the wild card represents authority to lend to any borrower,including groups. Lenders identified in the LenderID field 222 of alending authorization record 220 can be any lender, including, forexample, users and pools.

Borrowing for groups can be further explained with reference to theexemplary method of personal video recording depicted in FIG. 17. Themethod of FIG. 17 includes borrowing 408 from a lender 1502 a loanamount on behalf of a borrower 1514. The lender 1502 can be anyauthorized lender including, for example, individual users and pools.And the borrower 1514 can be any authorized borrower including, forexample, groups as well as individual users. In the context of ourexample data structures, an authorized borrower can be a group whosegroup ID appears in the BorrowerID field 224 of a lending authorizationrecord 220.

Loans from pools to groups are optional. That is, there is norequirement within the present invention for pools to loan to groups,and it is entirely within the scope of the present invention for a PVR'sprogramming to effect loans to groups only from individual users.

PVRs can be programmed to accept scheduling entries for shows orexpressions of group preferences from all group members or less thanall. The example data structure for member records 2106 includes aBoolean field AuthorizedRep 2110 in which is stored an indicationwhether the member represented by the member record 2106 is authorizedto schedule shows and assert preferences on behalf of the group.

FIG. 22 sets forth a flow chart depicting an exemplary method ofcreating a group. The method of FIG. 22 includes including creating 1906a group profile 2102 and assigning group storage space 1914 to thegroup. In addition, FIG. 22 depicts two alternative methods of assigninggroup storage space. More particularly, the method of FIG. 22 includesallocating 1908 to the group 2102 users' storage space 1904 as groupstorage space 1914. The method of FIG. 22 also includes the alternativeof assigning 1910 group storage space 1914 to the group 2102 directlyfrom unallocated storage space 1902.

To the extent that group allocation comes from members' free space 1904,members' allocated space (as reference 198 on FIG. 21 a) and members'free space (206 on FIG. 21 a) is reduced by the amount of storage spaceallocated from users' free space to group storage space. There is norequirement that members contribute equally to allocations from members'free space to group storage space. There no requirement that all (orany) users contributing free space to a group must be members of thegroup. Contributors, users and/or members can determine proportions ofallocation from users' free space when the group is created (or canamend later through user interface screens).

It is an advantage of the use of groups to record shows that the use ofindividual user's free space is leveraged. An example of such leveragingis a show having a storage space requirement of 50 megabytes recordedfor a group having three members each of whom contributed 20 megabytesof user free space to the group's storage space, that is, equalcontributions from each user. In this example, each user's free space isimplicitly used at the level of 16.67 megabytes in return for which eachuser is empowered to record and view a 50 megabyte show.

It is also an advantage that group ownership in shows implicitlyapportions ownership among members according to their relativecontributions to a group storage space. Consider an example in whichthree users group to record comedy shows knowing in advance that users 1and 2 have less interest in comedy that user 3. The users contributetheir free space to group storage space in the proportion 1/1/2, thatis, 10 megabytes from user 1, 10 megabytes from user 2, and 20 megabytesfrom user 3. In using 10 megabytes to record a show, therefore, thethree users implicitly use their storage space respectively at thelevels of 2.5 megabytes, 2.5 megabytes, and 5 megabytes. This is anexplicit use of group storage space that implicitly apportions the spacerequirement according to predetermined weighted coefficients, set by theusers themselves, rather than equally among all three members of thegroup.

Apportionment

In all our example thus far regarding groups, it is a group as a wholethat records and deletes each show, and, despite the implicitapportionment of storage space, it is nevertheless the group as a wholewho benefits from or suffers from the use of the show's entire spacerequirement at all times. It would be advantageous to have moreflexibility than that. It would be advantageous to be able to allowusers to aggregate their storage space in groups and then opt out userby user, with flexibility granted to each user when to opt out, ratherthan requiring the entire group to wait until they all recoup a show'sused space at the same time. It would be useful to be able to explicitlyapportion ownership, and loan amounts also, among members of a group.

Apportionment of Storage Space

We now describe an additional class of embodiments of PVRs according tothe present invention, embodiments for recording shows for groups inwhich a show's storage space requirement is charged to group membersrather than to a group as such. In such embodiments, with reference tothe example data structures in FIG. 21 a, to the extent that the dataelements for charging space requirements to groups, the fields for spaceallocation 2130, free space 2132, used space 2134, and borrowed space2136, are present in group profiles 2102, such fields are not utilized.Indeed, in some PVRs according to this class of embodiments, such fieldsmay be entirely excluded from group profiles 2102.

In other embodiments, two modes of operation are supported, one forcharging space requirements to a group as such, another mode forcharging space requirements to group members. In the first mode, thefields for charging space requirements to groups are utilized; in thesecond mode they are ignored. PVRs according to such embodiments canswitch between the two modes of operation using a mode switchimplemented, for example, in a Boolean field established for thatpurpose, such as, for example, the field GroupMode 2116 in the examplegroup profile 2102 on FIG. 21 a. We described the first mode ofoperation in detail above. In the description which follows, we focus onthe second mode, charging space requirements to members.

With reference to FIG. 23, and with reference to the example datastructures of FIG. 21 a, we described a method of personal videorecording of shows for groups that apportions 2156 storage spacerequirements 246 to group members 1920. The method of FIG. 23 includescreating 2106 show records 240 in two circumstances. The method includescreating show records when shows are scheduled for recording 2152through data entry by an authorized representative of a group 2108.

The method includes also creating show records when shows are identifiedfor preference recording 2154 on the basis of indications of memberpreference 2150. Members are users, and users, as described in detailabove, are supported by PVRs of the present invention in data entry ofindications of user preference, including, for example, entry into userpreference records 320 users' indications of preferred show titles 324and preferred actors 326, as well as users' indications of the relativeintensity with which such preferences are asserted, as, for example, inthe preference level field at reference 328.

A show 240 to be recorded on behalf of a group 2102 has stored in itsOwnerID field 244 the group ID of the group on whose behalf the show isto be recorded. In such embodiments, that group, rather than anyindividual user, is considered the owner of such a show.

FIG. 23 sets forth a flow chart depicting a method of automated personalvideo recording that includes recording 2162 for a group 2102 comprisinga number of members 1920, a show 240 having a storage space requirement246, wherein each of the members has allocated storage space 198 on aPVR optionally including free space 206. The method of FIG. 23 includesapportioning 2156 the show's storage space requirement 246, includingapportioning to each member 1920 an apportioned amount of the show'sstorage space requirement. Three exemplary alternative ways ofapportioning space requirements are disclosed.

In the method of FIG. 23, apportioning 2156 the show's storage spacerequirement 246 alternatively includes apportioning according to thenumber of members 2114. In PVRs according to this kind of embodiment,the number of members is typically recorded on a group profile 2102, in,for example, a field such as NumberMembers 2114. Apportioning a show'sstorage space requirement then includes dividing the show's spacerequirement by the number of members, thereby determining an apportionedamount of the show's storage space requirement to be charged to eachmember. Apportioning the show's storage space requirement then includesincrementing each member's UsedSpace 204 by the apportioned amount anddecrementing each member's FreeSpace 206 by the apportioned amount.

In the method of FIG. 23, apportioning 2156 the show's storage spacerequirement 246 alternatively includes apportioning according topredefined proportions 2160. In PVRs according to this kind ofembodiment, predefined proportions are established in fields such as theSpaceShare field 2112 in member records 2106. Predefined proportions canbe percentages adding up to one hundred percent, so that, for example,in a group having four members, the predefined proportions can be, forexample, 10%, 10%, 40%, and 40%. Apportioning a show's storage spacerequirement in such embodiments then includes multiplying the show'sstorage space requirement by each predefined proportion, therebydetermining a separate apportioned amount for each member. Apportioningthe show's storage space requirement in such embodiments then includes,for each member, incrementing a member's UsedSpace 204 by theapportioned amount for that member and decrementing a member's FreeSpace206 by the apportioned amount for that member.

In the method of FIG. 23, apportioning 2156 the show's storage spacerequirement 246 alternatively includes apportioning according tomembers' preferences 2158. Members indicate preferences in, for example,user preference records 320, including indications of levels of relativeintensity 328. Apportioning a show's storage space requirement in suchembodiments then includes establishing, as percentages, for example, aweighted coefficient of preference for each member. Apportioning ashow's storage space requirement in such embodiments then includesmultiplying the show's storage space requirement by each weightedcoefficient, thereby determining a separate apportioned amount for eachmember. Apportioning the show's storage space requirement in suchembodiments then includes, for each member, incrementing a member'sUsedSpace 204 by the apportioned amount for that member and decrementinga member's FreeSpace 206 by the apportioned amount for that member.

Further with regard to weighted coefficients of preference, we presentthis example for further explanation. In user preference records 320 forthe show title “Dukes of Hazzard,” Mom asserts a preference level of‘3,’ Dad asserts a preference level of ‘2,’ Son asserts a preferencelevel of ‘1,’ and Daughter asserts no preference for “Dukes of Hazzard.”The weighted coefficients of preference for the member respectively are3/6, 2/6, 1/6, and 0/6, or, in terms of percentages, 50%, 33.33%,16.67%, and 0%. The show's storage space requirement for an episode of“Dukes of Hazard” is 10 megabytes. The apportioned amount for eachmember respectively then is 5 megabytes, 3.3 megabytes, 1.67 megabytes,and 0 megabytes. In this example, the members' UsedSpace 204 isincremented and FreeSpace 206 is decremented in each member's userprofile 202 respectively by 5 megabytes for Mom, 3.3 megabytes for Dad,1.67 megabytes for Son, and 0 megabytes for Daughter. In this example,Daughter gets a free ride, which is reasonable in light of the fact thatshe expressed no preference for the show.

Members' Opting Out of Group-Related Allocations of Storage Space

Despite their prior agreement to join a group, it is possible thatmembers may wish to recoup their free space allocated to group storageof a show by opting out of the group's joint ownership of a show. Amember may wish to opt out and therefore recoup storage for other uses,for example, when the member has viewed a show. A member may wish to optout upon discovering that the group has recorded, and thereforeapportioned part of a show's storage requirement to the member, a showin which the member has little interest. Remember the example just abovein which the Son expressed a preference level of ‘1’ for “Dukes ofHazzard.” Upon learning that his group has recorded an episode of “Dukesof Hazzard,” the Son might very well believe this his storage spacemight be better utilized elsewhere.

In our teachings thus far regarding personal video recording, there isno very easy way for a member to opt out of group ownership of a show.Consider, for example, the case of storage space apportionment accordingto the number of members in a group. We disclosed storing the group sizein the NumberMembers field 2114 in a group profile 2102, shown on FIG.21 a. If the one member opts out, however, the effective group size isreduced by one. Presumably we could then define a field called forexample ‘EffectiveGroupSize’ in which a PVR could store the number ofmembers who have not opted out, but then there would be no easy way toknow which members remain. What is needed is something with moreflexibility.

FIG. 21 a depicts an example data structure for reapportionment records2174, each of which identifies a reapportionment of a show's storagespace requirement to a particular member of a group. Suchreapportionment records represent apportionments of responsibility for ashow's space requirement among the members of a group who have not optedout of ownership responsibility for a particular show. Usingreapportionment records 2174, a PVR is programmed to create, when a useropts out of group ownership, one reapportionment record for eachremaining member, thereby providing an exact record both of how manymembers remain as well as exactly which members remain.

The exemplary reapportionment record 2174 of FIG. 21 a provides a ShowIDfield 241 which functions as a foreign key relating the reapportionmentrecord to a show record 240. The show record 240 identifies a group asthe owner of the show by storing a group ID in its OwnerID field 244.The SpaceRequirement field 246 in the show record 240 stores the totalspace requirement of the show.

The exemplary reapportionment record 2174 provides a UserID field 280storing a user ID of one of the member to whom the show's storage spacerequirement is to be reapportioned. The exemplary reapportionment record2174 also provides a reapportionment amount field 282 storing theportion of the show's space requirement to be reapportioned to themember identified in the UserID field 280 of the reapportionment record2174.

FIG. 24 sets forth a flow chart depicting a method of personal videorecording in which group members are empowered to opt out of groupownership of shows. The method of FIG. 24 includes apportioning 2156 ashow's storage space requirement 246 among group members 1920.Apportioning 2156 storage space is carried out in dependence upon thenumber of members 2114, in dependence upon predefined proportions 2160,or in dependence upon members' preferences 2158. After apportioning 2156storage space, PVRs according to the method of FIG. 24 record the show2162, after which users optionally view the show (2164, 2170) and deletethe show 2172. Viewing the show is said to be optional in the sense thatthe show can be viewed before members opt out 2164, after members optout 2170, or, in fact, never viewed by anyone before the show is deletedfrom storage. The method of FIG. 24 does include eventually deleting theshow 2172, including reversing 2176 the then-current apportionments ofthe show's storage space requirement.

The method of FIG. 24 includes a member's opting out 2165 andsubsequently reapportioning 2166 the show's storage space requirement246 among group members 1920. Reapportioning 2166 the show's storagespace requirement includes reversing 2174 the previous apportionment ofthe show's storage space requirement by decrementing each member'sUsedSpace 204 by the original apportioned amount and incrementing eachmember's FreeSpace 206 by the original apportioned amount.

Reapportioning 2166 also includes creating 2168 reapportionment records2174, one reapportionment record for each group member remaining afterone opts out. Each reapportionment record 2174, as shown in FIG. 21 a,stores the show ID 241, a user ID of a remaining member, and areapportionment amount 282. Reapportionment amounts 282 are determinedin many ways. We discuss three exemplary alternative ways of determiningreapportionment amounts and then reapportioning storage spacerequirements accordingly.

In the method of FIG. 24, reapportioning 2166 the show's storage spacerequirement 246 alternatively includes reapportioning according to thenumber of members 2114. In PVRs according to this kind of embodiment,the number of members is typically recorded on a group profile 2102, in,for example, a field such as NumberMembers 2114. Reapportioning 2168 ashow's storage space requirement then includes decrementing by one thenumber of members, thereby determining the number of members remainingafter one opts out and the number of reapportionment records to becreated; creating one reapportionment record for each remaining member,described above; dividing the show's space requirement by the number ofremaining members, thereby determining a reapportioned amount of theshow's storage space requirement to be charged to each remaining member;and storing the reapportioned amount in the ReappAmount field 282 ineach reapportionment record 2174. Reapportioning the show's storagespace requirement then also includes incrementing each remainingmember's UsedSpace 204 by the reapportioned amount and decrementing eachremaining member's FreeSpace 206 by the reapportioned amount.

In the method of FIG. 24, reapportioning 2166 the show's storage spacerequirement 246 alternatively includes reapportioning according topredefined proportions 2160. In PVRs according to this kind ofembodiment, predefined proportions are established in fields such as theSpaceShare field 2112 in member records 2106. Predefined proportions canbe percentages adding up to one hundred percent, so that, for example,in a group having four members, the predefined proportions can be, forexample, 10%, 10%, 40%, and 40%. After a member opts out, however, theremaining members' predefined proportions no longer add up to 100%. Themethod of FIG. 24, therefore, includes recalculating by weight theremaining predefined proportions so that they again add up to 100%.Reapportioning a show's storage space requirement in such embodimentsthen includes multiplying the show's storage space requirement by eachrecalculated predefined proportion, thereby determining a separatereapportioned amount for each remaining member. Reapportioning a show'sstorage space requirement in such embodiments then includes storing eachremaining member's reapportioned amount in the ReappAmount field in areapportionment record 2174. Reapportioning the show's storage spacerequirement in such embodiments then includes, for each remainingmember, incrementing a member's UsedSpace 204 by the reapportionedamount for that member and decrementing a member's FreeSpace 206 by thereapportioned amount for that member.

In the method of FIG. 24, reapportioning 2166 the show's storage spacerequirement 246 alternatively includes reapportioning according tomembers' preferences 2158. Members indicate preferences in, for example,user preference records 320, including indications of levels of relativeintensity 328. Reapportioning a show's storage space requirement in suchembodiments then includes establishing, as percentages, for example, aweighted coefficient of preference for each remaining member. Theweighted coefficients so established will be different after a memberopts out, than they were before a member opted out, unless, as describedabove, the member opting out had asserted no preference for the show inquestion. Reapportioning a show's storage space requirement in suchembodiments then includes multiplying the show's storage spacerequirement by each newly established weighted coefficient, therebydetermining a separate reapportioned amount for each member.Reapportioning a show's storage space requirement in such embodimentsthen includes storing each remaining member's reapportioned amount inthe ReappAmount field in a reapportionment record 2174. Reapportioningthe show's storage space requirement in such embodiments then includes,for each remaining member, incrementing a member's UsedSpace 204 by thereapportioned amount for that member and decrementing a member'sFreeSpace 206 by the reapportioned amount for that member.

Apportionment of Loans

We now describe an additional class of embodiments of PVRs according tothe present invention, embodiments for recording shows for groups where,in addition to apportioning storage space requirements among members,loans of storage space are also apportioned among members. It is usefulto note that a need for a loan can arise in at least two ways. One way aneed for a loan can arise is when a deficit is discovered at the time ofa user-scheduled or recording or in preference recording.

Another way a need for a loan can arise is when a member opts out ofgroup ownership of a show. When a user opts out, the remaining members'apportioned amounts of the show's storage space requirement typicallywill increase. If one member's apportioned amount exceeds the member'sfree space, a deficit exists that requires borrowing if recording is tocontinue.

PVRs according to the embodiments under discussion charge group loanamounts by apportionment to group members rather than to a group assuch. If a member opts out, then any outstanding group loan amount isreapportioned to the remaining members.

With reference to the exemplary data structures of FIG. 3, a grouploans, that is, a loan to a groups, is authorized by storing a group IDin a BorrowerID field 224 in a lending authorization record 220. A datastructure useful in apportioning group loans among members is show inthe loan record 230 of FIG. 21 b. The loan record of FIG. 21 b issimilar to the loan record of FIG. 3 with the addition of a BooleanGroupLoan field 284, a field used for identifying a group loan. Moreparticularly, a group loan is represented by two types of loan recordsused in tandem. One loan record type, called a ‘group loan record,’ hasa group ID stored in its BorrowerID field 234 and its GroupLoan field284 is set to True. The other loan record type, called a ‘member loanrecord,’ has a group ID stored in its BorrowerID field 234 and itsGroupLoan field 284 is reset to False. Group loan records and memberloan records are therefore related one-to-many through the BorrowerIDfield 234 which stores a group ID operating as a relational key.

The LenderID field 232 in each member loan record stores a user ID of amember and therefore serves as a foreign key relating the member loanrecord to a user profile 202. From the point of view of the user profile202, the member loan record looks like any other loan record, but it isin fact a little different. The LoanAmount 236 in the member loan record230 represents an amount to be added to a member's BorrowedSpace 208 andsubtracted from a member's FreeSpace 206, just like any other loan to auser. There is a difference, however, because the only actual loan inquestion is one which was authorized as a loan to the group, in alending authorization record issued in favor of the group, not for anyparticular member of the group. The only loan involved here is a loan toa group. The LoanAmounts in the member loan records are apportionmentamounts of a group loan, not actual loans to individual members.

Described in the paragraphs just preceding is one exemplary way torepresent group loans in data structures. Another way would be to createa separate table for the header records, the group loan records. Manyother data structures for representing group loans will occur to thoseof skill in the art and all such structures are well within the scope ofthe present invention.

FIG. 25 sets forth a flow chart depicting a method of personal videorecording that includes apportioning or reapportioning 2112 a show'sstorage space requirement 246 to group members 1920. The members areusers having allocated storage space optionally including free space ona PVR. In the method of FIG. 25, comparing 2402 the members' apportionedamounts of storage space and the members' free space results in finding2406 at least one deficit, that is, at least one member whoseapportioned amount exceeds the member's free space by a deficit amount.

The method of FIG. 25 includes selecting 2407, in dependence upon thedeficit amount, one or more lenders 1502. The lenders 1502 can includeusers 1504 having free storage space and pools 1506 having free storagespace. The selecting 2407 is carried out in dependence upon the deficitamount in the sense that lenders are selected who have authorizedlending to the group in at least the deficit amount and who have freespace at least equal to the deficit amount. Alternatively, if there isno lender who authorizes lending to the group in at least the deficitamount and who has free space at least equal to the deficit amount, thenmore than one lender is selected.

The method of FIG. 25 includes borrowing 2408, in dependence upon thedeficit amount, from the lenders 1502 for the group, at least one loanamount of storage space. The borrowing 2408 is carried out in dependenceupon the deficit amount in the sense that a loan amount is borrowed atleast equal to the deficit amount. If there is no lender who authorizeslending to the group in at least the deficit amount and who has freespace at least equal to the deficit amount, then more than one loan iseffected with more than one loan amount until the total of the loanamounts is at least equal to the deficit amount.

The method of FIG. 25 include apportioning 2410 the loan amount amongthe group members 1920. Apportioning 2410 the loan amount among themembers includes apportioning to each member 1920 an apportioned amountof the loan amount. Three exemplary alternative ways of apportioningloan amount are disclosed below.

In the method of FIG. 25, apportioning 2410 the loan amountalternatively includes apportioning according to the number of members2114. In PVRs according to this kind of embodiment, the number ofmembers is typically recorded on, for example, a group profile 2102 in afield such as NumberMembers 2114 shown on FIG. 21 b. Apportioning a loanamount includes dividing the show's space requirement by the number ofmembers, thereby determining an apportioned amount of the loan amount tobe charged to each member. Apportioning a loan amount includes creating2411 loan records 230, including a group loan record and one member loanrecord for each member. Apportioning a loan amount includes storing inthe LoanAmount field 236 in each member loan record the apportionedamount to be charged to each member. Apportioning the loan amountincludes incrementing each member's BorrowedSpace 208 by the apportionedamount and decrementing each member's FreeSpace 206 by the apportionedamount.

In the method of FIG. 25, apportioning 2410 the loan amountalternatively includes apportioning according to predefined proportions2160. In PVRs according to this kind of embodiment, predefinedproportions are established in fields such as the SpaceShare field 2112in member records 2106. Predefined proportions can be percentages addingup to one hundred percent, so that, for example, in a group having fourmembers, the predefined proportions can be, for example, 10%, 10%, 40%,and 40%. Apportioning a loan amount in such embodiments includesmultiplying the loan amount by each predefined proportion, therebydetermining a separate apportioned amount for each member. Apportioninga loan amount includes creating 2411 loan records 230, including a grouploan record and one member loan record for each member. Apportioning aloan amount includes storing in the LoanAmount field 236 in each memberloan record the apportioned amount to be charged to each member.Apportioning the loan amount in such embodiments includes, for eachmember, incrementing a member's BorrowedSpace 208 by the apportionedamount for that member and decrementing a member's FreeSpace 206 by theapportioned amount for that member.

In the method of FIG. 25, apportioning 2410 the loan amountalternatively includes apportioning according to members' preferences2158. Members indicate preferences in, for example, user preferencerecords 320, including indications of levels of relative intensity 328.Apportioning a loan amount in such embodiments includes establishing, aspercentages, for example, a weighted coefficient of preference for eachmember. Apportioning a loan amount in such embodiments includesmultiplying the loan amount by each weighted coefficient, therebydetermining a separate apportioned amount for each member. Apportioninga loan amount includes creating 2411 loan records 230, including a grouploan record and one member loan record for each member. Apportioning aloan amount includes storing in the LoanAmount field 236 in each memberloan record the apportioned amount to be charged to each member.Apportioning the show's storage space requirement in such embodimentsthen includes, for each member, incrementing a member's BorrowedSpace208 by the apportioned amount for that member and decrementing amember's FreeSpace 206 by the apportioned amount for that member.

The method of FIG. 25 includes optionally recording the show 2120,optionally displaying the show 414, and eventually deleting the show2172, including canceling the loan 2502. Recording is said to beoptional in the method of FIG. 25 because, to the extent that the needfor borrowing is caused by a user's opting out of group ownership, theshow in question probably has already been recorded. Displaying (orviewing) the show 2172 is said to be optional in that an authorizedmember is perfectly free within the method of FIG. 25 to delete the showbefore anyone watches it.

Cancelling the loan includes scanning through the loan records 230 forthe show and, for the member identified in each member loan record,decrementing a member's BorrowedSpace 208 by the LoanAmount 236 for thatmember and incrementing a member's FreeSpace 206 by the LoanAmount 236for that member. Cancelling the loan then includes deleting all the loanrecords 230 for the show, that is, all the loan records related to theshow record through the ShowID field 241.

Members' Opting Out of Group-Related Loans of Storage Space

When a member opts out of responsibility for group ownership, not onlymust the storage space requirement be reapportioned (as described indetail above in this disclosure), but any existing loan amount must bereapportioned also. FIG. 26 sets forth a flow chart depicting a methodof personal video recording in which group members are empowered to optout of group ownership of a show when the show has an associated grouploan of storage space. The method of FIG. 26 includes a member's optingout 2165 after a PVR apportions 2410 a loan amount among group members1920.

There is no particular timing limitation on opting out. A member can optout before or after a show is recorded, before or after a show is viewedor displayed. When a member opts out therefore, it is possible, in factlikely, that the members' free space quantities have changed since therelated show record was created. The method of FIG. 26 includescomparing 2402 members currently apportioned amounts of the show'sstorage space and the members' free space to determine whether a deficitstill exists.

If members' free space has changed so that no deficit currently exists,then the method of FIG. 26 cancels 2502 the now unnecessary loan.Canceling the loan, as described above, includes scanning through theloan records 230 for the related show and, for the member identified ineach member loan record, decrementing a member's BorrowedSpace 208 bythe LoanAmount 236 for that member and incrementing a member's FreeSpace206 by the LoanAmount 236 for that member. Canceling the loan thenincludes deleting all the loan records 230 for the show, that is, allthe loan records related to the show record through the ShowID field241. After canceling the loan, the method of FIG. 26 is still left witha reduction in the number of members responsible for the show's storagerequirement, so the method includes reapportioning 2166 the show's spacerequirement among the remaining members as described in detail above.

If members' free space has not changed, so that a deficit still exists,of if members' free space has changed but nevertheless a deficit stillexists, the method of FIG. 26 proceeds by reapportioning 2604 the loanamount among the remaining members. Reapportioning the loan amountincludes reversing 2606 the current apportionment of the loan, deleting2608 the member loan record of the member opting out, and recalculatingthe 2610 members' apportioned amounts of the loan.

Reversing 2606 the current apportionment of the loan includes scanningthrough the loan records 230 for the related show and, for the memberidentified in each member loan record, decrementing a member'sBorrowedSpace 208 by the LoanAmount 236 for that member and incrementinga member's FreeSpace 206 by the LoanAmount 236 for that member. Then,because the method at this point is not canceling the loan entirely,only the member loan record for the member opting out is deleted 2608.

In the method of FIG. 26, reapportioning 2604 the loan amountalternatively includes recalculating 2610 apportioned amounts of thegroup loan according to the number of members 2114. In PVRs according tothis kind of embodiment, the number of members is typically recorded ona group profile 2102, in, for example, a field such as NumberMembers2114. Recalculating 2610 apportioned amounts of a loan then includesdecrementing by one the number of members, thereby determining thenumber of members remaining after one opts out. Alternatively, the PVRcan be programmed to determine the number of remaining members bycounting the number of member loan records remaining with the sameShowID setting, now that the member loan record of the member opting outhas been deleted. Recalculating 2610 then includes dividing the show'sspace requirement by the number of remaining members, therebydetermining a reapportioned amount of the loan to be charged to eachremaining member. The method includes storing the reapportioned amountin the LoanAmount field 236 in each remaining member loan record 230.Reapportioning the loan then also includes incrementing each remainingmember's UsedSpace 204 by the reapportioned amount and decrementing eachremaining member's FreeSpace 206 by the reapportioned amount.

In the method of FIG. 26, reapportioning 2604 the loan amountalternatively includes recalculating 2610 apportioned amounts of thegroup loan according to predefined proportions 2160. In PVRs accordingto this kind of embodiment, predefined proportions are established infields such as the SpaceShare field 2112 in member records 2106.Predefined proportions can be percentages adding up to one hundredpercent, so that, for example, in a group having four members, thepredefined proportions can be, for example, 10%, 10%, 40%, and 40%.After a member opts out, however, the remaining members' predefinedproportions no longer add up to 100%. Recalculating 2610 apportionedamounts of a loan therefore includes recalculating by weight theremaining predefined proportions so that they again add up to 100%.Recalculating 2610 in such embodiments then includes multiplying thetotal loan amount by each recalculated predefined proportion, therebydetermining a separate reapportioned amount for each remaining member.Recalculating 2610 in such embodiments then includes storing eachremaining member's reapportioned amount in the LoanAmount field 236 in aremaining member loan record 230. Recalculating 2610 in such embodimentsthen includes, for each remaining member, incrementing a member'sUsedSpace 204 by the reapportioned amount for that member anddecrementing a member's FreeSpace 206 by the reapportioned amount forthat member.

In the method of FIG. 26, reapportioning 2604 the loan amountalternatively includes recalculating 2610 apportioned amounts of thegroup loan according to members' preferences 2158. Members indicatepreferences in, for example, user preference records 320, includingindications of levels of relative intensity 328. Recalculating 2610apportioned amounts of a group loan in such embodiments then includesestablishing, as percentages, for example, a weighted coefficient ofpreference for each remaining member. The weighted coefficients soestablished generally will be different after a member opts out, thanthey were before a member opted out, unless, for example, as earlierdescribed in detail, the member opting out asserted no preference forthe show in question. Recalculating 2610 in such embodiments thenincludes multiplying the total loan amount by each newly establishedweighted coefficient, thereby determining a separate reapportionedamount for each remaining member. Recalculating 2610 in such embodimentsthen includes storing each remaining member's reapportioned amount inthe LoanAmount field 236 in a remaining member loan record 230.Recalculating 2610 in such embodiments then includes, for each remainingmember, incrementing a member's UsedSpace 204 by the reapportionedamount for that member and decrementing a member's FreeSpace 206 by thereapportioned amount for that member.

Recovery Of Displayed Storage Space

In this specification so far, our discussion has assumed that, if ashow's storage space requirement exceeds available free space and it isnot possible find a lender so that storage space can be borrowed, thenthe show will not be recorded. See, for example, our discussion aboveregarding the method depicted in FIG. 4 in which a failure to select alender 406 results in stopping recording 412.

See also, for example, our discussion above regarding the methodsdepicted in FIGS. 11 and 12, both of which are concerned with the riskof underestimating a show's storage space requirement. Both methodsinclude stopping recording (464, 412) if no lender can be found (462,406). See also our discussion of apportioning or reapportioning storagespace requirement among group members in connection with FIG. 25, whereonce again we assumed that a failure to find a lender 2407 would meanstopping recording 2409.

It would be advantageous, however, if there were other ways to find orcreate additional free space, so that recording can continue over abroader range of circumstances and storage space can be used moreefficiently. One way to proceed against this problem is to note that atany given moment, used space may store recorded shows portions of whichhave already been displayed to viewers. It would be useful to have waysof recovering such displayed storage space for current use in recordingshows.

In the following discussion, we use the terms “displayed storage space”or “displayed space” to refer to the storage space upon which isrecorded portions of shows that have already been displayed to viewers.FIG. 27 depicts exemplary data structures useful in freeing displayedspace for use in recording shows. PVRs according to embodiments of thisinvention are programmed to refrain from attempting to free displayedspace in shows that are marked as write-protected, as, for example, inthe Boolean fields DefaultRecordProtect (2762 on user profile 202),RecordProtect (2758 on show record 240), and DefaultRecordProtect (2760on PVR profile 300). DefaultRecordProtect 2762 and DefaultRecordProtect2760 are Boolean indications, at the user level and the PVR levelrespectively, whether to set RecordProtect 2758 to True as a default,that is, whether the default for the PVR is to exclude recoveringdisplayed space for use in further recording. An indication whether aparticular show is write-protected, such as, for example, theRecordProtect field 2758, can be changed at any time by an authorizeduser through manipulation of a user interface. The defaults can bechanged also.

DisplayStartTime 2750 and DisplayStopTime 2752 record display start timeand display stop time respectively for a display period for a show 240.The amount of used space that has been displayed for the show can bestored in DisplayedSpace 2766, or the amount of displayed space can becalculated on the fly as described in more detail below.

DisplayStartTime 2754 and DisplayStopTime 2756, in the viewing records250, record display start time and display stop time respectively for adisplay period for a show identified in ShowID 252 for a particular useras identified in ViewerID 254. The amount of used space that has beendisplayed for the show to the user can be stored in DisplayedSpace 2764or can be calculated on the fly as described below.

FIG. 28 depicts an exemplary method of freeing displayed storage spacefor use in recording shows. More particularly, FIG. 28 depicts a methodfor automated personal video recording on a personal video recorder. Themethod of FIG. 28 includes recording 2702 a first show 2710; displaying2704 at least a portion of the first show, thereby creating displayedspace 2712; freeing 2706 displayed space, thereby making available freespace 2714; and recording 2708 at least part of a second show 2716 infree space 2714 made available by freeing displayed space.

FIG. 29 depicts a method of personal video recording in which a show'sstorage space requirement is compared 403 with a borrower's free space.The method includes selecting 406 lenders when the borrower's free spaceis less than the show's storage requirement, that is, when a deficitexists. In a similar method discussed above in connection with FIG. 4,when lenders are successfully selected, a PVR according to thisembodiment borrows a loan amount at least covering the deficit 408 andproceeds with recording 410. If no lender is found, recording stops 412.In the method of FIG. 29, however, there is an additional alternative.That is, the method of FIG. 29 includes borrowing less than the deficit2950, freeing displayed space 2706, and then proceeding with recording410. Freeing displayed space 2706 comprises freeing a sufficientquantity of displayed space so that the displayed space so freed incombination with the borrowed loan amount 2950 is sufficient to meet thedeficit. In use of the method of FIG. 29, it is only necessary to stoprecording 411 in the event that both borrowing 2950 and freeingdisplayed space 2706 fail to provide sufficient free space to meet thedeficit.

In the method of FIG. 28, the first show 2719 and the second show 2716can be same show. FIG. 30 depicts, in a flow chart and a schematicdiagram of storage space requirements, an alternative method of freeingdisplayed space of a show while recording and viewing a show. In FIG.30, the step 2708 for recording a second show includes recording asecond show 2906 in free space 2714 made available by freeing 2706displayed space 2904 of a first show 2902. In addition, the step 2709for recording a second show includes recording a second show 2902(actually the first show) in free space 2714 made available by freeing2706 displayed space 2904 of a first show 2902. That is, the methoddepicted in FIG. 30 includes operation by recording a show into space inwhich an earlier portion of the same show was recorded, displayed, andsubsequently freed. This can occur when, for example, in the process ofchecking a storage space requirement during recording of a show that isbeing viewed while it is being recorded, a PVR finds a deficit. If theonly displayed space available to be freed is the earlier-displayedportion of the same show, then the PVR frees that displayed space andcontinues recording.

Referring again to FIG. 28, note that if a PVR is to free 2706 displayedspace, the PVR will need to be able to identify displayed space to free.Displaying a show 2704, therefore, in the example of FIG. 28, includesidentifying the displayed space 2718 for the show. FIG. 31 depicts inmore detail a method of identifying 2718 displayed space for a show.More particularly, the method of FIG. 31 includes storing 2802 in aviewing record 280, for a show identified by ShowID 252, a display starttime 2808 and a display stop time 2810 for a display period for a theshow. The method of FIG. 31 includes subtracting 2804 the start time2808 from the stop time 2810, thereby establishing a duration 2812 for adisplay period for the show. The method of FIG. 31 also includesmultiplying 2806 the duration 2812 of the display period by a frame rate2814 for the show, thereby identifying, in terms of a number of videoframes, a particular amount of displayed space 2712 for the show.

Consider, for example, a thirty-minute show displayed at a frame rate ofthirty frames per second having a display period of ten minutes. In thisexample show, there are 10 minutes×60 seconds/minutes×30 frames/secondequals 18,000 displayed frames. That is, the displayed space for such ashow can be represented as comprising the first 18,000 frames of thevideo file in which the show is recorded. If the show's storage spacerequirement is 60 megabytes, then the displayed space for the show canalternatively be represented as comprising one third of the show'sstorage space requirement or 20 megabytes of displayed space.

The PVR needs the frame rate for calculating displayed space in terms ofvideo frames. PVRs according to some embodiments of the presentinvention store the frame rate 2766 for a show directly on the showrecord 240. Other embodiments treat frame rate as one factor incompression level 279 and store frame rates in tables keyed bycompression level, such as, for example, the tables depicted in FIG. 10a and 10 b. PVRs implementing the method of FIG. 28, for example,typically include identifying frame rates in dependence upon compressionlevels of shows, that is, inferring or identifying frame rates fromcompression level tables such as those of FIGS. 10 a and 10 b.

In the method of FIG. 28, freeing displayed space comprises discarding2720 displayed frames. As shown in FIG. 28, one way to discard displayedframes is to issue video editing calls 2722 to software routines in anapplication programming interface (“API”) for video editing, a videoediting API. There are many APIs for video editing. Most, if not all,codecs have associated APIs for video editing. Examples of APIs forvideo editing include ‘Video For Linux,’ Microsoft's ‘Video ForWindows™,’ and the Sun Microsystems's ‘Java Media FrameworkTm.’ VideoFor Windows, for example, is a hardware independent API used by popularvideo editing packages such as Adobe Premier™ and by video conferencingsoftware such as Microsoft's NetMeeting™.

FIG. 32 depicts an alternative exemplary method of discarding 2720displayed frames, a method that is implemented by applicationprogramming that itself directly manipulates video files or manipulatesvideo files through calls to video editing APIs. The method of FIG. 32operates on a show 2710 recorded in a video file 3102 comprising videoframes 3104, including displayed frames 3106. In the method of FIG. 32,discarding 2720 displayed frames comprises deleting 3110 displayedframes from the video file. More particularly, the method of FIG. 32includes opening 3108 the video file 3102; deleting 3110 displayedframes 3106; and closing 3112 the video file 3106. The method of FIG.32, therefore, relies on the PVR's operating system to reduce the sizeof the video file 3102 by approximately the proportion of storage spaceformerly occupied by the deleted displayed frames 3106.

FIG. 33 depicts a slightly more affirmative alternative exemplary methodof discarding 2720 displayed frames, a method that too is implemented byapplication programming that itself directly manipulates video files ormanipulates video files through calls to video editing APIs. The methodof FIG. 33 operates upon a show in an original video file 3102comprising video frames 3104 and displayed frames 3106. In the method ofFIG. 33, discarding 2720 displayed frames comprises streaming 3306 theshow from the original video file 3102 to a new video file 3312,excluding displayed frames 3106, and deleting 3310 the original videofile 3102. More particularly, the method of FIG. 33 includes opening3202, the original video file 3202; opening 3304 a new video file 3312;streaming 3306 the video frames 3104 from the original video file 3102to the new video file 3312, excluding displayed frames 3106; closing3308 the new video file 3312; and deleting 3310 the original video file3102. We say that this method is slightly more affirmative in that thenew video file 3312 is only ever filled with a video clip of reducedsize, and the original video file 3102 is completely deleted.

In all this opening, closing, and deleting of files, in PVRs accordingto many embodiments of the present invention, the application softwarein a PVR will need the shows' filenames for dealing with the PVR'soperating system. Shows' filenames are stored, for example, in fieldsprovided for that purpose, such as the one at reference 242 in showrecord 240 on FIG. 27. In the method of FIG. 33, for example, it isuseful, after opening a new video file 3312 and deleting 3310 theoriginal video file 3102, for the PVR to update the filename field 242(presently containing the filename of the original video file 3102) inthe show record 240 with a filename for the new video file 3312.

It is useful to consider in more detail the process of deletingdisplayed frames and excluding displayed frames from a stream to a newvideo file as these processes apply to discarding displayed frames. Moreparticularly, it is useful to identify how to determine when to stop.That is, it is useful to have particular ways of determining in deletingdisplayed frames which is the last frame to be deleted, assuming the PVRtakes as the first frame to be deleted the first frame in the videofile. Similarly, with respect to excluding displayed frames from a steamto a new file, it is useful to be able to identify exactly which frameis to be the last frame excluded from the stream to the new file,assuming that the PVR begins exclusion with the first frame in theoriginal video file. The answer as to which frame is the last framedepends on the video encoding of the video being worked upon, the filefrom which frames are to be deleted or the file from which frames arestreamed to a new file.

MJPEG, for example, compresses only a single frame at a time, so-calledintra-frame or spatial compression. Each MJPEG video frame is a completepicture in itself. Identifying a particular MJPEG frame as the lastframe to be deleted or excluded a stream is straightforward: Count thenumber of frames identified by use of, for example, the method of FIG.31 for identifying displayed space 2718. That is, multiply 2806 aduration 2812 of a display period by a frame rate 2814 for a show. Theproduct is a number of frames. In using a method according to FIG. 32,delete that number of frames from the front of a video file. In using amethod according to FIG. 33, exclude that number of frames from thefront of a stream from an original video file to a new video file.

MPEG, on the other hand, is an inter-frame compression format that usesboth spatial compression in each frame and temporal compression acrossframes. In MPEG, that is, several frames at once are considered whileperforming encoding operations. FIG. 34 illustrates a simplifiedillustrative example of the structure of MPEG-1 video. MPEG-1 videoincludes a sequence header 3402, followed by one or more alternatingsequences of ‘Group of Pictures’ or ‘GOP’ headers 3404 and GOPs 3406,followed by a sequence end marker 3408. A GOP is a series of pictures(frames 3416) each of which consists of a picture header and actualpicture data.

A frame or picture can be of type I(3410), P (3412), or B (3414). AnI-frame is an ‘intracoded’ frame, intracoded meaning coded only withreference to itself. I-frames are coded spatially with no reference toany other frame in the sequence. That is, I-frames are coded spatiallybut not temporally. I-frames can be decoded, or reconstructed fordisplay, with no reference to other frames. Each I-frame is a completepicture ready for display on its own after decoding.

Starting with an I-frame, an MPEG encoder can forward predict a futureframe. A forward-predicted frame is called a ‘P-frame,’ ‘P’ for‘predicted.’ P-frames are predicted from I-frames and from otherP-frames. P-frames are encoded both spatially and temporally. It is notpossible to reconstruct or decode a P-frame without data from anotherframe. P-frames are forward predicted only, from the most recentlypreceding I-frame or P-frame.

B-frames are both forward predicted and backward predicted, ‘B’ for‘bidirectional.’ B-frames are forward and backward predicted from thelast and next I-frame or P-frame, therefore requiring two other framesto reconstruct each encoded B-frame.

As an example of the usage of I, P, and B-frames, consider the followingsequence of six-frame GOPs: IBPBPB, IBPBPB, IBPBPB . . . The I-framesare coded spatially only and the P-frames are forward predicted based onprevious I and P-frames. The B-frames are coded based on forwardprediction from a previous I or P-frame, as well as backward predictionfrom a succeeding I or P frame. The example sequence is processed by theencoder so that the first B frame is predicted from the first I frameand first P frame; the second B frame is predicted from the second andthird P frames; and the third B frame is predicted from the third Pframe and the first I frame of the next group of pictures.

Note that the second B-frame in each GOP, in addition to depending onbackward prediction from a next I-frame, also depends on forwardprediction from a preceding P-frame which in turn depends on forwardprediction from a preceding P-frame and a preceding I-frame. Because theP-frames and B-frames between I-frames depend, directly or indirectly,on forward prediction from a previous I-frame, cutting an MPEG sequenceat a point in the sequence between I-frames renders useless the framesbetween the cut point and the next I-frame. Cuts for deleting displayedframes from MPEG video files and excluding displayed frames from MPEGstreams in PVRs according to embodiments of the present invention,therefore, are usefully made at I-frames.

With reference to the methods of FIG. 32 and 33, therefore, PVRsaccording to those methods usefully include, when processing MPEG video,in the process of deleting 3110 displayed frames 3106 and in the processof streaming 3306 while excluding displayed frames 3106, checking frametypes. Frame types are checked in such embodiments, for MPEG video, todetermine that the first frame in continuation is an I-frame, that is,that the next frame after a last frame deleted or excluded is anI-frame, so that an MPEG decoder in reconstructing the modified or newfile for display is not presented initially with a P-frame or a B-frame,frames which cannot be decoded without a preceding I-frame.

In other words, if the last frame to be deleted or excluded is a P-frameor a B-frame, then PVRs processing MPEG video according to theseembodiments can delete all the frames up to the next I frame. If the cutwould then occur in the middle of GOP, requiring editing a GOP header,then PVRs can delete or exclude all the frames up to the beginning ofthe next GOP, including the GOP header for the current GOP. A typicalMPEG block frame count is sixteen frames including one I-frame. Onaverage, this method therefore would be expected to exclude about eightundisplayed frames comprising about a fourth of a second of videodisplay, which is unlikely to be noticed by viewers.

An alternative for MPEG that is slightly more conservative and slightlymore complex is to buffer GOPs, that is, buffering all the frames ineach GOP one-by-one as each GOP is processed for deletion or exclusion.Then when a displayed frame count indicates a mid-GOP discard, the PVRcan still include or stream out to the new video file the entire currentGOP, including the displayed frames in the GOP as well as theundisplayed frames in the block, thereby deleting somewhat fewer thanall the displayed frames, but conservatively preserving all the framesnot yet displayed.

We discussed in this disclosure several ways of carrying out deletionsand exclusions of displayed frames, particularly with reference to theexemplary encodings MJPEG and MPEG. Many ways of deleting or excludingdisplayed frames in these encodings and other encodings will occur tothose of skill in the art, and all such ways are well within the scopeof the present invention.

Further Compression of Shows

Above in this disclosure, we discussed various ways of making free spaceavailable for recording shows, including lending free space to otherusers or groups of users, repossessing loaned space, and recovery ofdisplayed space. We discussed also the fact that compression levelsaffect storage space requirements and storage space usage. In light ofthat discussion, we note now that it would be useful also to be able,not only to calculate and reset storage space requirements in dependenceupon compression levels, but also to affect compression levels as such.Having the capability of changing compression levels for shows alreadyrecorded or currently in the process of being recorded would add auseful alternative way of making free space available for recording.

We turn now to a discussion of further compression of shows. We speak of“further” compression because, as readers will realize from our earlierdiscussion of compression, all shows are compressed to some extentduring delivery or capture and storage. Readers will also understand bynow that in this discussion the term “show” includes show records thatidentify shows and store the shows' attributes, as well as thephysically recorded video and audio content associated with particularshows. Although it is true that the physically recorded content can bestored in a variety of media including streams and temporary datastructures in RAM, for ease of explanation, we generally speak in thisdisclosure of recording shows in files for storage in file systems onmagnetic or optical media.

FIG. 35 depicts a method for automated personal video recording thatincludes recording 3502 shows (3504, 3505), where each show has anoriginal compression level 3506. Compression level values generally,including the original compression level 3506 of this embodiment, can bestored, for example, in a compression field such as the one illustratedat reference 279 in the show record 240 in the example data structuresin FIGS. 3 and 27. The method of FIG. 35 includes further compressing3508 a recorded show 3505 to a new compression level 3510, the newcompression level being higher than the recorded show's originalcompression level, thus making free space 3512 available for recording.The method of FIG. 35 also includes recording 3516 at least part of anew show 3514 in free space 3512 made available by further compressingthe recorded show 3505.

The need to make additional free space available for recording can arisein several ways. Additional free space is needed for scheduled recordingand for preference recording when, for example, a show to be recordedfor a user has a storage space requirement larger than the user's freespace. Additional free space is needed for apportioning andreapportioning shows' storage space requirements among group members,when, for example, an apportioned amount of a storage space requirementexceeds a member's free space. Additional free space is needed forapportioning and reapportioning group loan amounts among group members,when, for example, an apportioned amount of a loan exceeds a member'sfree space.

FIG. 36 depicts a method of personal video recording in which a show'sstorage space requirement is compared 403 with a borrower's free space.When the borrower's free space is less than the show's storagerequirement, that is, when a deficit exists 404, the method proceeds byselecting 406 lenders. In a similar method discussed above in connectionwith FIG. 4, when lenders are successfully selected, a PVR according tothis embodiment borrows a loan amount at least covering the deficit 408and proceeds with recording 410. If no lender is found, recording stops412. In the method of FIG. 36, however, there is an additionalalternative. The method of FIG. 36 includes borrowing less than thedeficit 2950, further compressing 3508 a recorded show, and thenproceeding with recording 410. Further compressing 3508 a recorded showincludes freeing a sufficient quantity of displayed space so that thedisplayed space so freed in combination with the borrowed 2950 loanamount is sufficient to meet the deficit. In use of the method of FIG.36, it is only necessary to stop recording 411 in the event that bothborrowing 2950 and further compressing 3508 recorded shows fail toprovide sufficient free space to meet the deficit.

In addition to the method of further compressing recorded shows, PVRscan implement also the method of FIG. 29 comprising freeing displayedspace 2706. In such PVRs, it is only necessary to stop recording 411 inthe event that the combination of borrowing 2950, freeing displayedspace 2706, and further compressing recorded shows 3508 fails to providesufficient free space to meet a deficit.

A further kind of embodiment, illustrated also in FIG. 35, includesselecting a recorded show to be further compressed. Selecting therecorded show can include selecting a show having an originalcompression level lower than a highest supported compression level in aPVR. The recorded show's ‘original’ compression level is the compressionlevel presently stored in the compression field 279 show's show record240. Regarding the relationship between the original compression leveland the highest supported compression level, consider, for example,compression level table 602 in FIG. 10 b. Assume for explanation thatthe original compression level is ‘320:1,’ indicating the compressionlevel whose affecting factors are listed in record 606 of table 602,including MPEG-2 encoding, a frame rate of 30 frames per second, aresolution of 352×240, and so on. The compression level of ‘320:1’ isrelative to raw video. The same compression level is ‘4’ relative to anNTSC source stream identified in record 604 of table 602.

The highest supported compression level, in this example context, is‘20480:1.’‘Highest supported compression level’ means the highest levelfor which a PVR has a codec capable of handling the show's presentencoding as an input and producing a more compressed encoding of videoas output. In this example context, such a ‘highest supportedcompression level’ is indicated in record 614 of table 602. As long asthe show's original compression level is less than a highest supportedcompression level, the show is a candidate for further compression. Inthis example, as among several candidate shows, selecting a show forfurther compression includes selecting the first show among thecandidates having an original compression level lower than a highestsupported compression level in a particular PVR according to anembodiment of the present invention.

The method of FIG. 35 includes further compressing a recorded show. Therecorded show comprises an original video file, ‘original’ in the sensethat it is in a beginning condition for the current process of furthercompression. As shown in FIG. 35, one way to further compress theoriginal video file is to issue calls 2722 to software routines in anapplication programming interface (“API”) for a codec. There are manyAPIs for codecs. Most, if not all, codecs have associated APIs. Examplesof APIs for codecs, as mentioned earlier, include ‘Video For Linux,’Microsoft's ‘Video For Windows™,’ and the Sun Microsystems's ‘Java MediaFramework™.’

FIG. 37 depicts a method of further compressing 3508 a recorded showcomprising an original video file 3702. The method of FIG. 37 isimplemented by application programming that itself directly manipulatesvideo files or manipulates video files through calls to codecs' APIs.Although it is possible through application programming to manipulatevideo files directly, because of the complex structure of most videoencoding formats, it is quite likely that most embodiments willimplements codecs and codec APIs. In the following discussion, the useof codecs and codec APIs is assumed.

In the method of FIG. 37, a recorded show comprises an original videofile 3702 having original encoding parameters 3704 including an originalencoding type 3706. Examples of encoding type include MPEG-1, MPEG-2,MPEG-4, MJPEG, DVD, and so on. Further compressing 3508 the recordedshow includes opening 3718 the original video file 3702, opening 3720 anew video file 3710, converting 3708, through a codec 176, the originalvideo file 3702 into a new video file 3710 having new encodingparameters 3712.

Encoding parameters implement factors affecting compression level,including, as illustrated, for example, in FIGS. 10 a and 10 b, encodingtype 424, color space size 426, frame rate 428, resolution 430, andaudio quality 432. The new encoding parameters may optionally include anew encoding type 3714, although it may or may not be necessary tochange encoding type in order to achieve a higher compression level. Inthe sequence of compression levels depicted in table 602 in FIG. 10 b,for example, beginning with an original compression level of 320:1 forthe MPEG-2 encoding type, there are two higher compression levels havingthe MPEG-2 encoding type (represented by records 608 and 610) that canbe used before there is a need to change to MPEG-1 (record 612) or MJPEG(record 614) in order to obtain even higher compression.

In addition, when changing encoding types, it may or may not benecessary to change codecs. At least some codecs that handle MPEG-2 alsohandle MPEG-1, for example. Our system block diagram in FIG. 2 a depictsonly one codec 176, but that illustration is for convenient explanation,not for limitation. PVRs according to embodiments of the presentinvention often will implement more than one codec. In situationsrequiring changes in encoding type to achieve higher supportedcompression levels, a series of codecs are used to convert from oneencoding type or compression level to another.

The method of FIG. 37 includes closing 3722 the new video file 3710 anddeleting 3716 the original video file 3702. The PVR may give the newvideo file 3710 a filename different from the filename of the originalvideo file 3702, and, to the extent that it does so, then the PVR can beprogrammed to update the filename field 242 in the show record 240 withthe new filename of the new video file 3710. In addition, the PVR alsois programmed to update the compression field 279 on the show record 240with the new compression level resulting from the change in the encodingparameters.

Regarding changing compression levels, our discussion thus far hascentered on changes for existing recorded shows. It would be usefulalso, however, to have ways of changing compression level duringrecording, if, for example, a need for additional free space isdiscovered during a check of an estimated storage space requirement. Ifthere were at that time no other useful or desirable way of quicklyfreeing space for continuing recording, it would be useful to be able toincrease compression ‘on-the-fly,’ so to speak.

FIG. 38 depicts a method for administration of storage spacerequirements on a PVR that includes recording 3800 a show 3802 having acompression level 279 and increasing 3806 the show's compression level279 while recording 3800. The show includes a duration 247 andincreasing 3806 the show's compression level includes tracking 3802 arecording period for the show and tracking actual storage space usedduring the recording period. When the tracked recording period is atleast equal to a space check threshold multiplied by the duration 3810,the method of FIG. 38 proceeds to compare 3804 the storage space usedwith an amount of storage space projected to be used during the trackedrecording period. If the storage space used is greater than the storagespace projected to be used, the method increases 3806 the show'scompression level.

FIG. 39 depicts a more detailed exemplary method of increasing 3806 ashow's compression level during recording. The method of FIG. 39includes recording 3800 a show includes encoding 3902 a video stream3922 through a codec (not shown) to a first video file 3906. Theencoding 3902 is carried out in dependence upon values of factorsaffecting compression level, that is, in dependence upon codec operatingparameters 3904. In the method of FIG. 39, increasing 3806 the show'scompression level includes closing 3908 the first video file 3906,opening 3910 a second video file 3923, and changing 3912 the values ofthe codec operating parameters 3904, thereby changing the compressionlevel of the second video file with respect to the first video file.

More particularly, the codec operating parameters are changed so as toincrease the compression level. Again with reference to FIG. 10 b,consider an example in which the first video file is encoded with codecoperating parameters that effect the compression level identified byrecord 606 in table 602. That is, the codec is an MPEG codec set toencode an MPEG-2 video file having a frame rate of 30 frames per second,a resolution of 352×240, and so on, all resulting in a compression levelof 320:1 with respect to raw NTSC video. Changing 3912 the values of thecodec operating parameters 3904 to increase the compression level from320 to 1280 then includes calling the codec API with the new operatingparameters of record 608, that is, in this example, changing theresolution to 180×120.

The method of FIG. 39 includes calling the codec API with a filename forthe second video file, thereby redirecting 3914 the video stream 3922 tothe second video file 3923. The method also includes closing 3916 thesecond video file 3923 at the end of the show and further compressing3918 the first video file 3906 to the compression level of the secondvideo file. The first video file 3906 is stored at its originalcompression level. If the show as a whole is to be effectivelycompressed so that it can be decoded for display through a single codec,it is useful to convert the entire show, including the first portion ofthe show stored in the first video file to the new higher compressionlevel of the second video file.

Alternatively, it is possible within the scope of the present inventionto leave a single show fragmented among more than one video file, eachvideo file having different encoding parameters. PVRs implementing thisalternative then would need to expand the data structures representingshows (see FIG. 3) to include file-related information, such as filename and compression level, for each file comprising a show. Such PVRswill need to be programmed to change files, change parameters, andperhaps even change codecs to decode, during display, a show comprisingmore than one video file.

Among embodiments that leave a show fragmented among more than one videofile, recording is simplified by reducing, or even eliminating, the needto further compress the first video file to the compression level of thesecond video file and concatenate the two files. On the other hand,decoding a show for display is easier if the show is encoded at recordtime into a single video file, because there is no need during playbackto track and change video files, change codec parameters, or changecodecs. In addition, further compressing the first video file at recordtime increases the amount of free space made available by changing to ahigher compression level. Some increases in compression level, such as,for example, changes in audio quality, have no effect on video playbackquality, although they may affect other aspects of playback.Nevertheless, leaving the show fragmented in more than one file havingmore than one compression level may affect display quality if the showis later replayed, changing display quality when playback changes fromthe first video file to the second video file, particularly when changesin resolution or frame rate were required in order to effect aparticular increase in compression level.

The exemplary method of FIG. 39 includes further compressing 3918 thefirst video file 3906 and concatenating 3920 the second video file 3923to the first video file 3906. Concatenating the video files typicallyincludes calls to codec APIs to effect orderly changes in sequenceheaders, GOP headers, and so on. Although we refer in this specificationto concatenating the two video files, readers of skill in the art willrecognize that in fact such concatenating may include combining througha codec two source streams from the first video file and the secondvideo file into a target stream directed to a third video file.

We have now discussed in this disclosure several ways of furthercompressing or increasing compression of shows in PVRs. Many ways offurther compressing or increasing compression of shows in PVRs willoccur to those of skill in the art, and all such ways are well withinthe scope of the present invention.

It will be understood from the foregoing description that modificationsand changes may be made in various embodiments of the present inventionwithout departing from its true spirit. The descriptions in thisspecification are for purposes of illustration only and are not to beconstrued in a limiting sense. The scope of the present invention islimited only by the language of the following claims.

1. A method for automated personal video recording, the methodcomprising the steps of: recording shows, each show having an originalcompression level; further compressing a recorded show to a newcompression level, the new compression level being higher than therecorded show's original compression level, making available free space;recording at least part of a new show in free space made available byfurther compressing the recorded show, wherein the new show's storagespace requirement exceeds an amount of free space available forrecording the new show by a deficit amount; and borrowing a loan amount,the loan amount being less than the deficit amount.
 2. The method ofclaim 1 further comprising selecting the recorded show.
 3. The method ofclaim 2 wherein selecting the recorded show comprises selecting a showhaving an original compression level lower than a highest supportedcompression level in a personal video recorder.
 4. The method of claim 1wherein the recorded show comprises an original video file and furthercompressing the recorded show comprises calling software routines in anAPI for a codec.
 5. The method of claim 4 wherein the recorded showcomprises an original video file having original encoding parametersincluding an original encoding type, and further compressing therecorded show comprises: converting the original video file into a newvideo file having new encoding parameters optionally including a newencoding type; and deleting the original video file.
 6. A personal videorecorder (“PVR”) comprising: means for recording shows, each show havingan original compression level; means for further compressing a recordedshow to a new compression level, the new compression level being higherthan the recorded show's original compression level, making availablefree space; means for recording at least part of a new show in freespace made available by further compressing the recorded show, whereinthe new show's storage space requirement exceeds an amount of free spaceavailable for recording the new show by a deficit amount; and means forborrowing a loan amount, the loan amount being less than the deficitamount.
 7. The PVR of claim 6 further comprising means for selecting therecorded show.
 8. The PVR of claim 7 wherein means for selecting therecorded show comprises means for selecting a show having an originalcompression level lower than a highest supported compression level inthe PVR.
 9. The PVR of claim 6 wherein the recorded show comprises anoriginal video file and means for further compressing the recorded showcomprises means for calling software routines in an API for a codec. 10.The PVR of claim 9 wherein the recorded show comprises an original videofile having original encoding parameters including an original encodingtype, and means for further compressing the recorded show comprises:means for converting the original video file into a new video filehaving new encoding parameters optionally including a new encoding type;and means for deleting the original video file.
 11. A computer programproduct for automated personal video recording, the computer programproduct comprising: a recording medium; means, recorded on the recordingmedium, for recording shows, each show having an original compressionlevel; means, recorded on the recording medium, for further compressinga recorded show to a new compression level, the new compression levelbeing higher than the recorded show's original compression level, makingavailable free space; means, recorded on the recording medium, forrecording at least part of a new show in free space made available byfurther compressing the recorded show, wherein the new show's storagespace requirement exceeds an amount of free space available forrecording the new show by a deficit amount; and means, recorded on therecording medium, for borrowing a loan amount, the loan amount beingless than the deficit amount.
 12. The computer program product of claim11 further comprising means, recorded on the recording medium, forselecting the recorded show.
 13. The computer program product of claim12 wherein means, recorded on the recording medium, for selecting therecorded show comprises means, recorded on the recording medium, forselecting a show having an original compression level lower than ahighest supported compression level in a personal video recorder. 14.The computer program product of claim 11 wherein the recorded showcomprises an original video file and means, recorded on the recordingmedium, for further compressing the recorded show comprises means,recorded on the recording medium, for calling software routines in anAPI for a codec.
 15. The computer program product of claim 14 whereinthe recorded show comprises an original video file having originalencoding parameters including an original encoding type, and means,recorded on the recording medium, for further compressing the recordedshow comprises: means, recorded on the recording medium, for convertingthe original video file into a new video file having new encodingparameters optionally including a new encoding type; and means, recordedon the recording medium, for deleting the original video file.